Skip to main content
Glama
Sign In
gpsem

gpsem

by puples
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Tableau de bord Screaming Frog

getScreamingFrogDashboard
Read-onlyIdempotent

Retrieve a Screaming Frog crawl dashboard to analyze crawl quality, prioritized issues, top recommended actions, and most affected pages for a site.

Instructions

Tableau de bord Screaming Frog — Crawl, qualité du crawl, problèmes par catégorie avec priorité et score, 12 actions prioritaires, pages les plus touchées. — (GET /sites/{siteId}/screaming-frog)

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": {
      "siteId": "<siteId>"
    },
    "name": "getScreamingFrogDashboard"
  }
}

Input Schema

NameRequiredDescriptionDefault
crawlNoID du crawl (défaut : dernier crawl importé)
siteIdYesID site encodé (hashid)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is clear. The description adds what content is returned but not behavioral traits such as default crawl handling, data freshness, or response format; this is acceptable but not richly transparent.

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?

The description is compact and enumerates the dashboard contents efficiently. However, it starts by repeating the title 'Tableau de bord Screaming Frog' and appends the endpoint as metadata, which adds minor redundancy rather than value.

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?

There is no output schema, so the description must carry some return expectations. It lists the main components, but it does not describe the structure, score scale, priority representation, or how the optional crawl parameter affects results, leaving meaningful gaps for an agent.

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 100%, so both siteId and crawl are already documented. The description does not add parameter-level meaning beyond that, and the baseline of 3 is appropriate since the schema carries the semantic load.

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 states the tool returns a Screaming Frog dashboard with crawl, crawl quality, categorized issues with priority and score, 12 priority actions, and most affected pages. This is concrete and specific, though it is phrased as a noun phrase rather than a clear verb like 'Récupère' and does not explicitly compare itself to sibling detail tools.

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?

The 'Tableau de bord' wording implies this is for a high-level dashboard view, but the description does not say when to use this tool instead of listScreamingFrogActions, listScreamingFrogCrawls, or getScreamingFrogIssue. No exclusions or alternative-routing guidance is provided.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools