Skip to main content
Glama

ADS Beast

seo_site_check

Positions, technical state and a prioritised task list for a client's site; the tasks are saved in ADS Beast.

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

Input Schema

NameRequiredDescriptionDefault
client_idYes
website_urlNoSite URL; the client's own site by default.

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=false, destructiveHint=false and openWorldHint=true, so the description's main added value is explaining WHY it is not read-only: 'the tasks are saved in ADS Beast', a persistent side effect the agent would otherwise miss. It still omits practical behavior such as runtime/cost, whether the save is idempotent or creates duplicates on repeat runs, and what the saved tasks attach to.

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?

A single compact sentence with no filler, and the interesting detail (persisted tasks) is attached via the semicolon. It is readable but front-loads a list of outputs instead of an action, which slightly weakens scanability.

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 does well to sketch the return (positions, technical state, prioritised tasks) and the side effect. For an open-world, non-read-only tool with an undocumented required parameter, though, it should say more about what the check covers and what the persisted tasks mean for repeated calls.

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 coverage is only 50%: website_url is documented in the schema, but client_id is a bare integer with no description anywhere. The description says nothing about either parameter — it never states that client_id scopes the run to one client or that omitting website_url defaults to that client's own site, even though that default materially changes results.

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 (a client's site) and enumerates outputs — positions, technical state, a prioritised task list — so an agent can tell it is an SEO site-check. However, it is phrased as a noun list rather than a verb+resource statement ('Run a site SEO check' appears only in the annotation title), and it does not distinguish itself from close siblings such as seo_on_page_audit or seo_performance_report.

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 explicit when-to-use guidance, no prerequisites, and no naming of an alternative tool for overlapping needs (on-page audit, performance report, rank tracking). The agent must infer that this is the broad 'check everything about a site' entry point from the word 'site' alone.

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.