Skip to main content
Glama

Outil.io

Capture site images

capture_site_images
Read-only

Captures de PLUSIEURS pages en un appel (vue d’ensemble par format, rendues en parallèle). Chaque bloc porte son repère @ref incrusté et le snapshot est renvoyé : ce qui se voit se corrige directement par apply_site_changes, sans clic ni relecture de structure. Pour lire un détail : capture_page_images mode tiles + sectionRefs.

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": {
      "pageIds": "<pageIds>"
    },
    "name": "capture_site_images"
  }
}

Input Schema

NameRequiredDescriptionDefault
labelsNoIncruster le repère @ref de chaque bloc (défaut) ; false pour un rendu propre
sourceNodraft
devicesNo
pageIdsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / devices / items / enum
      Previous value: -[
      -  "desktop",
      -  "tablet",
      -  "mobile"
      -]New value: +[
      +  "desktop",
      +  "mobile"
      +]
    • changedInput schema / properties / devices / maxItems
      Previous value: -3New value: +2
  2. Changed1 schema field changed
    • addedInput schema / properties / labels
      Added value: +{
      +  "default": true,
      +  "description": "Incruster le repère @ref de chaque bloc (défaut) ; false pour un rendu propre",
      +  "type": "boolean"
      +}
  3. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so safety is covered. The description adds real behavior: renders run in parallel, @ref markers are baked into each block by default, and the snapshot is returned so fixes go straight through apply_site_changes. It stops short of describing the response shape beyond "snapshot", which is the only meaningful gap.

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?

Three sentences, front-loaded with the core capability and ending with the alternative routing, with no filler. The middle sentence is somewhat long and chains several ideas, but every clause carries information.

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

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a four-parameter, non-destructive capture tool with no output schema, the description covers scope, rendering behavior, markup, and the next step. What's missing is parameter-level context (pageIds bounds, draft vs published) and any sense of what the returned snapshot looks like.

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 coverage is only 25% (just the labels parameter is documented), so the description has to compensate. "Vue d'ensemble par format" hints that devices drive per-format renders and the @ref marker language relates to the labels flag, but pageIds (max 8) and source (draft/published) get no explanation anywhere.

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

Purpose5/5

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

"Captures de PLUSIEURS pages en un appel" names a concrete verb, resource, and scope (multi-page overview, parallel renders). The final sentence explicitly distinguishes it from capture_page_images, so an agent can pick the right capture tool without opening either schema.

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

Usage Guidelines5/5

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

It states the condition for this tool (broad overview across pages/formats) and the condition for the alternative ("Pour lire un détail : capture_page_images mode tiles + sectionRefs"). It also routes the follow-up action to apply_site_changes, so the full workflow is implied.

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.