Skip to main content
Glama

resume_refresh

Resume failed or interrupted refresh jobs by reprocessing only unfinished sources; skip completed ones and reuse the saved publication window and profile.

Instructions

Resume failed/interrupted sources of a durable job, skipping every completed source.

Reuses the saved publication window and profile even if the profile was edited/deleted. An already running or completed job is unchanged.

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": {
      "job_id": "<job_id>"
    },
    "name": "resume_refresh"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and discloses meaningful behavior: completed sources are skipped, the saved publication window and profile are reused even if the profile was edited or deleted, and running/completed jobs are untouched. It omits side effects on job status and any permission requirements, but the no-op behavior is unusual and valuable context.

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?

Front-loaded with the action, then two short sentences each contributing a distinct behavioral fact. No filler, though the dense second sentence packs two separate facts together.

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?

The tool is a state-changing operation with no annotations, one simple parameter, and an output schema that covers return values. The description adequately explains what is resumed, what is skipped, and the profile-reuse edge case; only auth/permission context is missing.

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 schema has 0% description coverage and one parameter (job_id), which the description never mentions. job_id is largely self-evident from the schema title and the job-oriented tool name, but the description does not compensate for the coverage gap by explaining valid job identities.

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?

States a specific verb+resource: resuming failed/interrupted sources of a durable job, with scope ('skipping every completed source') that separates it from a full start_refresh. Sibling differentiation is inferable rather than explicit, so it falls short of a 5.

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

Usage Guidelines4/5

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

The description makes the use case clear (recovering failed/interrupted work) and adds a when-not condition: an already running or completed job is left unchanged. No alternative tool is named for starting a fresh job, which keeps it out of 5 territory.

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