Skip to main content
Glama

xpay✦ Marketing Collection

scrapecreators_search_for_companies

Search for Companies

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesKeyword to search for

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

C2/5.0
Behavior1/5

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

No annotations exist, and the description gives no behavioral details such as whether the operation is read-only, what data is returned, pagination, or rate limits. The phrase 'Search for Companies' only states the action without any transparency about side effects or output.

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

Conciseness2/5

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

The description is extremely short but under-specified; it does not earn its place as it merely paraphrases the tool name. There is no structured information or added value, making it a case of under-specification rather than effective conciseness.

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

Completeness2/5

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

With a single parameter, no output schema, and no annotations, the description offers nothing beyond the tool name. For a search tool that presumably returns companies, it does not explain result format, search scope, or any limitations, making it insufficient for an agent to invoke correctly.

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

Parameters3/5

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

The only parameter 'query' is fully documented in the schema with the description 'Keyword to search for'. The tool description adds no further meaning, so the schema carries the burden; baseline 3 applies.

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

Purpose2/5

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

The description 'Search for Companies' is a near-verbatim restatement of the tool name, providing no additional specificity about the data source, platform, or result type. It does not differentiate from sibling tools like scrapecreators_advertiser_search or scrapecreators_search.

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

Usage Guidelines2/5

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

No usage guidance is provided; there is no indication of when to prefer this tool over the many sibling search tools, nor any exclusion criteria. The description is silent on context or alternatives.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources