search_goods_services
Full-text search over the goods/services recitations of 14M USPTO marks — answers "who else claims X in their goods?" (competitive landscape, descriptiveness/crowded-field evidence, ID-drafting precedent). Keyword-based: the text is tokenized and matched against each mark's indexed goods keywords...
This record as markdown: /tools/com-gleanmark-trademark-search/search-goods-services.md
What search_goods_services does on GleanMark Trademark Search
AI agents call search_goods_services to retrieve information from GleanMark Trademark Search without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
mode | string | — | list_marks returns rows; count returns totals + class/status breakdowns only; top_owners ranks owners by matching-mark count. |
sort | string | — | |
text | string | Yes | Goods/services text to search for (e.g. "anti-tarnish", "vegan leather handbags"). Words of 3+ characters are matched as keywords. |
limit | integer | — | Max rows for list_marks mode (default 20). |
match_mode | string | — | all = every keyword must appear in the recitation (default); any = at least one. |
nice_classes | array | — | Optional Nice class filter (e.g. [14] or ["014"]). |
status_filter | string | — | live = Registered + Pending; dead = Cancelled/Abandoned/Expired. |
owner_contains | string | — | Optional: only marks whose owner name contains this text. |
Parameters from the server's own tool schema.
Why search_goods_services is rated Low
Even though search_goods_services only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs search_goods_services safely
PolicyLayer is an MCP gateway: it sits between your AI agents and GleanMark Trademark Search, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For search_goods_services, this is the rule to start with:
search_goods_services is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect GleanMark Trademark Search, apply this rule, and every search_goods_services call is checked against it from then on.
Questions about search_goods_services
Full-text search over the goods/services recitations of 14M USPTO marks — answers "who else claims X in their goods?" (competitive landscape, descriptiveness/crowded-field evidence, ID-drafting precedent). Keyword-based: the text is tokenized and matched against each mark's indexed goods keywords (match_mode all = every keyword must appear, any = at least one). Rows return a short excerpt around the matched clause, NOT the full recitation. mode=count answers "how many marks claim X" with class/status breakdowns; mode=top_owners ranks the owners claiming X — neither pulls rows. This searches goods/services TEXT, not mark names — for mark-name conflicts use run_knockout_search or search_trademarks. It is categorised as a Read tool in the GleanMark Trademark Search MCP Server, which means it retrieves data without modifying state.
search_goods_services accepts 8 parameters: mode, sort, text, limit, match_mode, nice_classes, status_filter, owner_contains. Required: text. The full parameter table on this page comes from the server's own tool schema.
Register the GleanMark Trademark Search MCP server in PolicyLayer and add a rule for search_goods_services: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches GleanMark Trademark Search. Nothing to install.
search_goods_services is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the search_goods_services rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for search_goods_services. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
search_goods_services is provided by the GleanMark Trademark Search MCP server (https://gleanmark.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on GleanMark Trademark Search, and thousands of servers like it.
This server
Across the catalogue