Skip to main content
Resolve up to 25 brand names, domains, URLs, topics, markets, places (“Austin, TX”), or question wordings to Parse ids (brd_, top_, mkt_, plc_, qst_, pg_, site:), with match score and index status. Use match: “meaning” for semantically nearest questions, topics, or markets to a text or id. Use kinds: [“facet”], [“surface”], [“measure”], or [“argument”] alone for the dictionary of valid filter facets, AI surfaces, metric definitions, or extra tool arguments. Free.

Who may call it, and what it costs

Price. Free. Every reply says what the call cost in meta.costCredits. The prices are on Spending, tracking and stopping.

Arguments

list of string
names, domains, URLs, question wordings or typed ids (up to 25); match: “meaning” takes one text or qst_/top_/mkt_ id; the dictionary takes words to look for, or none; kinds argument takes tool names up to 25
list of one of brand, topic, question, market, page, site, place, facet, surface, measure, argument
what to match: brand, topic, question, market, page, site, place (default all); with match: “meaning” question, topic, market; or facet, surface, measure alone for the dictionary; argument alone, with tool names in q: what a tool takes beyond its tools/list entry up to 7
one of name, meaning
name (default): exact names, domains and ids; meaning: nearest in meaning, for a phrase with no exact match or to find what to track next
one of brand, answer, mention, evidence, comparison, page, page_brand, question, topic_brand
dictionary only: facets of this unit (answer, mention, evidence, comparison, page, page_brand, question, topic_brand)
object
match: “meaning” only: within these markets or topics
list of string
Industry or category markets. For countries use country, and for cities use place. up to 50
list of string
up to 50
string
match: “meaning” only: brd_ id, adds its share named in each result (90 days)
boolean
match: “meaning” only: leave out what this workspace tracks
number
match: “meaning” only: 0.3 to 0.99, default 0.6 min 0.3, max 0.99
integer
match: “meaning” only: default 10 min 1, max 50
one of compact, full
compact (≈6k tokens, default) or full (≤20k)
list of string
columns to keep in each row up to 40
boolean
false: leave out the one-sentence note (data.note)
Every argument the tool takes, as GET /v1/tools serves it, every shared object written out; https://agent.parse.gl/openapi.json serves the same schema with the filter and the window named once under components and pointed to by $ref. MCP tools/list leaves out the arguments few calls send, and says the filter and the window once, under search_answers; resolve_ids {"kinds": ["argument"]} lists what it left out, and a call with any of them runs:

Example call

Find a brand by its domain, with its markets and whether Parse has enough on it. Over REST:
Over MCP, the assistant calls the tool by name with the same arguments:
More calls:
  • Find a place’s plc_ id: {"q":["Austin, TX"],"kinds":["place"]}
  • Find the questions Parse already asks that mean the same: {"q":["best project management tool for agencies"],"match":"meaning","kinds":["question"],"limit":5}
  • The dictionary: every field to filter and group by, every AI surface and every measure: {"kinds":["facet"]}
  • Only the facets of a brand mention: {"kinds":["facet"],"unit":"mention"}
  • The arguments search_answers takes beyond those its tools/list entry shows: {"kinds":["argument"],"q":["search_answers"]}
The reply has data, context, next, page and meta; follow next for the calls that come after. A refused call returns { code, message, fix }: see the error table.