Skip to main content
Glama

ADS Beast

seo_performance_report

Read-only

An SEO and AI-visibility report for a client or domain. AI: 1 AI request.

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_performance_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainNoDomain without scheme.
periodNoweekly, monthly or quarterly.monthly
client_idNo
report_typeNoexecutive, marketing, technical or client.marketing

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered elsewhere. The description does add a genuinely useful non-schema signal with 'AI: 1 AI request', a cost signal absent from annotations, but it omits whether the report is generated synchronously, how long it takes, or whether it is persisted somewhere.

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 short sentences with no filler, and the core purpose is front-loaded. The 'AI: 1 AI request' fragment is terse to the point of being cryptic in its placement, but it costs almost nothing.

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?

There is no output schema, so the description is the only place an agent could learn what a report invocation returns, and it says nothing about format or contents. For a report-generation tool with four optional parameters and no required fields, leaving output shape and default-selection behavior unstated leaves a real gap.

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 75%, and both enums (period, report_type) carry their own inline descriptions, so the schema does most of the work. The description only gestures at the client_id/domain distinction without explaining precedence when both are provided. Baseline 3 is appropriate here.

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 a resource and scope ('SEO and AI-visibility report for a client or domain'), which is more than a tautology, but it never says what the report contains or what producing it means. With siblings named report_create and prepare_client_report_send in the catalog, an agent cannot tell from this text which reporting tool to pick.

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, no exclusions, and no mention of the alternatives. The phrase 'for a client or domain' hints at two input modes but does not state when each is appropriate or what happens if both/neither are supplied.

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.