mcp-server

search_target_categories

Read-onlyIdempotent

Search a feed's target taxonomy tree (marketplace categories) by a substring of the category path. Use this to find the target category id for a mapping. Address the taxonomy by feed_id (its taxonomy is used) OR explicitly by taxonomy_code (+ optional taxonomy_locale). Returns {categories:[{hash, name, path}], returned, total, taxonomyCode, taxonomyLocale}; pass a returned hash as target_hash to set_category_mapping. query matches the full path (e.g. 'laptop', 'shoes'); limit bounds the results (default 50). project_id is OPTIONAL (inferred for a single-project customer).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "search_target_categories"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Max categories to return (default 50).
`query`	Yes
`feed_id`	No
`project_id`	No
`taxonomy_code`	No	Target taxonomy id (e.g. 'google'); alternative to feed_id for addressing the taxonomy.
`taxonomy_locale`	No	Locale of the taxonomy tree, e.g. 'en_GB' — defaults to the taxonomy's own default when omitted.

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 1, 2026

TDQS

A4.7/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnly/idempotent/non-destructive, yet the description still adds substantive behavior: the exact return envelope, the meaning of `hash`, the chaining instruction to pass it as target_hash to set_category_mapping, and that project_id is inferred for single-project customers.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with purpose, then usage, then return shape and parameter notes — logical ordering with no filler. Minor redundancy: restating the default of 50 for `limit`, which the schema already documents.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 6-parameter read tool with no output schema, the description supplies the return structure, the downstream chaining step, the two taxonomy addressing modes, and the optional-project caveat. Nothing an agent needs to call it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 50%, but the description compensates: `query` matches the full path with examples, `limit` bounds results, feed_id vs taxonomy_code are framed as explicit alternatives, taxonomy_locale is optional, and project_id is flagged OPTIONAL and inferred. This is near-complete parameter guidance beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: 'Search a feed's target taxonomy tree (marketplace categories) by a substring of the category path.' The parenthetical disambiguates it from the store-side taxonomy siblings (list_store_categories, list_unmapped_categories), so an agent can select it without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit reason to call it ('Use this to find the target category id for a mapping') and explains the two ways to address the taxonomy (feed_id vs taxonomy_code + taxonomy_locale). It stops short of naming the sibling to use for the opposite direction (e.g. store categories), so no explicit when-not guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All mcp-server tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?