Skip to main content
Glama

Sextant Web - Website GEO, SEO, and Analytics

Import progress

imports_status
Read-onlyIdempotent

The progress of one import (importId), or of the latest import of the site: status (fetching, writing, done, failed, undoing, undone), percent, days and page views written, notes and errors. Admin.

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

Input Schema

NameRequiredDescriptionDefault
siteIdYes
importIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive behavior, and the description goes beyond them by enumerating the status lifecycle (fetching, writing, done, failed, undoing, undone) and the fields reported (percent, days and page views written, notes, errors). It also flags the Admin auth requirement, which annotations do not cover. It stops short of explaining consistency of a failed/undoing import or how to interpret percent.

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 dense sentence with the default/fallback behavior front-loaded right after the resource. Nothing is redundant, though the parenthetical status list and the trailing 'Admin.' make it read as telegraphic rather than flowing prose.

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 two-parameter read-only status tool with no output schema, the description covers the returned status values and reported fields, so an agent knows what comes back. Missing pieces are minor: percent scale, and whether statuses like 'undoing' are terminal.

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 0%, so the description must carry parameter meaning, and it does explain the critical one: providing importId targets a specific import while omitting it falls back to the site's latest import. siteId is left to the name alone, which is reasonable but undocumented. The compensation is partial rather than complete.

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?

Names the resource (import progress) and the two addressing modes precisely: 'one import (importId)' or 'the latest import of the site'. An agent can distinguish this from imports_list, which presumably enumerates imports rather than reporting progress. The only weakness is that the verb is nominal ('the progress of') rather than an explicit action, but the intent is unambiguous.

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?

Usage is implied rather than stated: an agent infers it should call this to poll a running import and omit importId to check the site's most recent one. It does signal the 'Admin' permission requirement, which is useful gating context. There is no explicit guidance on when to prefer this over imports_list or on polling cadence.

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.

Resources