Skip to main content
Glama

ADS Beast

competitor_social_signals

Read-only

A competitor's recent activity outside its site: YouTube, blog feed, public posts and community mentions.

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": {
      "competitor_url": "<competitor_url>",
      "client_id": "<client_id>"
    },
    "name": "competitor_social_signals"
  }
}

Input Schema

NameRequiredDescriptionDefault
client_idYes
competitor_urlYesCompetitor's site.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so safety and open-world nature are covered. The description adds the channel coverage (YouTube, blog, public posts, community mentions), which is useful context beyond the annotations. It does not say how 'recent' is defined, whether results are paginated, or whether external API keys are needed for an open-world scrape.

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

Conciseness3/5

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

A single sentence fragment with no wasted words, but the terseness comes at the cost of missing a verb and any operational detail. It is front-loaded only in the sense that it leads with the resource.

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?

This is an open-world, read-only retrieval tool with no output schema and only half the parameters documented. The description omits how far back 'recent' reaches, what the response shape is, and how client_id affects results – gaps the agent cannot fill from structured fields.

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

Parameters2/5

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

Schema description coverage is only 50%: competitor_url is documented ('Competitor's site') but client_id is not. The description adds no meaning for either parameter – it never mentions the competitor URL input or what client_id scopes. With low coverage, the description should compensate and does not.

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

Purpose3/5

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

The description names the resource and its scope ('activity outside its site: YouTube, blog feed, public posts and community mentions'), which does separate it from site-analysis siblings. But it is a noun phrase with no verb – it never says whether the tool fetches, lists, or summarizes these signals. An agent knows the topic but not the operation.

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 when-to-use guidance, no prerequisites, and no alternatives named. The phrase 'outside its site' implicitly contrasts with competitor_site_analyze, but the agent is left to infer when to reach for this vs. competitor_search_intel or competitor_ads_research.

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.