Skip to main content
Glama

ADS Beast

seo_research

Read-only

Keyword clusters, audience pain points, pre-purchase questions and competitor analysis for a client's site. Takes minutes. AI: 1 AI request. May return a job_id (get_job_result).

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

Input Schema

NameRequiredDescriptionDefault
client_idYes
max_parallelNoSites read in parallel, 1-8.
competitor_urlsNoCompetitor domains without scheme.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint and destructiveHint=false, so the description adds genuinely new context on top: expected latency ("Takes minutes"), cost ("AI: 1 AI request") and the asynchronous contract where a job_id may be returned and must be resolved via get_job_result. That async behavior is the single most consequential thing an agent needs and is not derivable from the annotations or schema. It stops short of saying how long results persist or whether results are cached per client.

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?

Three short sentences, front-loaded with the deliverable list, so an agent sees the value proposition first. The telegraphic fragments ("AI: 1 AI request") are efficient but slightly cryptic; a few more characters would remove ambiguity at no real cost to length.

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

Completeness4/5

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

With no output schema, the description carries the return-value burden and does so by enumerating the four result categories, plus it discloses the async job pattern and rough runtime. What remains thin is the client_id contract and the behavior when competitor_urls is absent, but for a read-only research trigger the agent has enough to call it and know what to expect.

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?

Schema coverage is 67%: max_parallel and competitor_urls are already documented in the schema, and the description adds nothing about them — notably it does not say what happens when competitor_urls is omitted. The required client_id is undocumented in both schema and description, so an agent gets no help identifying where that integer comes from. At middling coverage, a baseline 3 is appropriate.

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 deliverables (keyword clusters, pain points, pre-purchase questions, competitor analysis) and scopes them to a client's site, which tells an agent what data comes back. But it never states a verb or the form of the result — it is a noun phrase list, not a statement that this runs research and returns a report. It also overlaps conceptually with siblings like seo_keyword_research and seo_competitor_analysis without saying how this bundled tool differs.

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?

There is no when-to-use guidance and no exclusions — nothing says to pick this over the narrower seo_keyword_research or seo_competitor_analysis tools. The only routing hint is the post-call behavior (job_id → get_job_result), which is a continuation instruction rather than a selection guideline.

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.