Skip to main content
Glama
Sign In
gpsem

gpsem

by puples
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Plan d'action Screaming Frog

listScreamingFrogActions
Read-onlyIdempotent

Retrieve prioritized SEO corrective actions from Screaming Frog audits, covering template, content, and highly linked URL issues. Filter by crawl, category, or priority to resolve site problems.

Instructions

Plan d'action Screaming Frog — Actions correctives priorisées (gabarit, contenu, URL très liées). — (GET /sites/{siteId}/screaming-frog/actions)

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": "listScreamingFrogActions"
  }
}

Input Schema

NameRequiredDescriptionDefault
crawlNoID du crawl (défaut : dernier crawl importé)
siteIdYesID site encodé (hashid)
prioriteNo1 à 4
categorieNoCatégorie d'audit

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already cover the safety profile (read-only, idempotent, non-destructive). The description adds useful behavioral context by saying actions are prioritized and categories are template/content/highly-linked URLs, but it does not explain ordering criteria, pagination, output shape, or the dependency on a crawl.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is very short, but the opening phrase 'Plan d'action Screaming Frog' largely repeats the tool title, and the endpoint suffix adds little. It is not overlong, yet part of the text does not earn its place.

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?

For a simple read-only listing tool with one required parameter and strong annotations, the description is minimally adequate. However, with no output schema, it does not describe the response structure, and it offers no selection guidance among the many audit/Screaming Frog sibling tools.

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?

The input schema has 100% description coverage, so every parameter (siteId, crawl, priorite, categorie) is already documented. The description adds no extra parameter semantics, but the baseline of 3 is appropriate because the schema carries the 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 identifies a specific resource — the Screaming Frog action plan — and states that it returns prioritized corrective actions grouped by categories (template, content, highly linked URLs). It is clear enough to distinguish from crawling/dashboard siblings, though it does not explicitly call out any sibling tool.

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 guidance on when to use this tool versus alternatives such as listAuditActions, getScreamingFrogDashboard, or getScreamingFrogIssue. The description does not mention prerequisites like an existing crawl or explain how this differs from other audit/action tools.

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