Skip to main content
Glama

ADS Beast

seo_content_gap

Read-only

Topics competitors cover and this site does not, with an action plan. AI: 1 AI request. May return a job_id (get_job_result).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "seo_content_gap"
  }
}

Input Schema

NameRequiredDescriptionDefault
geoNoCountry: SK.
nicheNoBusiness niche or industry, in plain words.
domainNoDomain without scheme.
client_idNo
competitorsNoCompetitor domains, comma-separated.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false. The description adds value beyond them by disclosing the AI cost ('1 AI request') and the asynchronous behavior (may return a job_id to be resolved with get_job_result), which an agent cannot infer from the annotations.

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?

Two compact sentences with the deliverable front-loaded and the cost/async caveats second. Nothing is wasted, though the parenthetical '(get_job_result)' is slightly telegraphic.

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

Completeness3/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 must carry the return-value burden; it names the deliverable and the job_id path but says nothing about the structure of the action plan or how many topics are returned. For a five-parameter, AI-cost-incurring analysis tool, that is adequate but not thorough.

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 description coverage is 80%, so the schema already documents geo, niche, domain, and competitors, and the description adds no parameter meaning on top. Notably, all five parameters are optional, and the description does not clarify what minimally constitutes a valid call (domain vs client_id), leaving a real ambiguity.

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

Purpose4/5

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

The description names a specific analytical resource: topics competitors cover that this site does not, delivered with an action plan. It is clearly an analysis output rather than a write or audit, but it does not explicitly contrast itself with nearby sibling analyses such as seo_competitor_analysis.

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

Usage Guidelines3/5

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

Usage is implied by the phrase 'competitors cover and this site does not', but there is no explicit when-to-use or when-not-to-use guidance relative to sibling tools. The one concrete routing hint is the follow-up instruction that a job_id should be resolved via get_job_result, which is useful but covers only the post-call path.

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.