Skip to main content
Glama
Sign In
webEmbedding

webEmbedding

by jongko54
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

list_clone_jobs

Read-onlyIdempotent

Retrieve persisted clone jobs from a filesystem-backed async queue and filter by state to monitor queued, running, or failed website cloning tasks.

Instructions

List persisted clone jobs from the filesystem-backed async queue.

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": {
      "queue_root": "<queue_root>"
    },
    "name": "list_clone_jobs"
  }
}

Input Schema

NameRequiredDescriptionDefault
statesNoOnly return jobs in these states: queued, retry_wait, running, succeeded, failed, blocked, needs_session, manual_review, cancelled.
queue_rootYesDirectory holding the filesystem job queue; created if missing.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.3.13
    • addedInput schema / properties / queue_root / description
      Added value: +"Directory holding the filesystem job queue; created if missing."
    • addedInput schema / properties / states / description
      Added value: +"Only return jobs in these states: queued, retry_wait, running, succeeded, failed, blocked, needs_session, manual_review, cancelled."
  2. First observedv0.3.12

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so the safety profile is covered; the description adds useful context that the queue is filesystem-backed and persisted. It does not disclose ordering, result limits, or what happens with an empty/nonexistent queue directory beyond what the schema says about creation.

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 front-loaded sentence with zero filler or redundancy. Its brevity borders on under-specification rather than verbosity, but nothing in it needs trimming.

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 two-parameter read-only listing tool with full schema coverage and annotations, the description is adequate but thin. With no output schema present, it could have said what a returned job entry looks like or whether results are ordered, and it omits any guidance on the relationship to load_clone_job.

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 100%, with both queue_root and the states filter fully documented including the enumerated state values, so the description need not compensate. It adds no meaning about the states filter or queue_root beyond the schema, which is the correct baseline when the schema does the work.

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 and resource ('List persisted clone jobs') plus the backing store ('filesystem-backed async queue'), which separates it from single-job siblings like load_clone_job or cancel_clone_job. It stops short of naming a sibling explicitly, so it is clear but not fully differentiated.

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?

The description gives no when-to-use guidance, no prerequisites, and no indication of when to prefer load_clone_job or inspect_url instead. Only a weak implication of 'enumerate all jobs' comes from the word 'List'.

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