Skip to main content
Glama
Sign In
webEmbedding

webEmbedding

by jongko54
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

run_clone_job

Executes one website cloning queue job, or picks the next due queued/retry-wait job when no ID is provided, so workers can process cloning tasks in order.

Instructions

Run one clone queue job, or the next due queued/retry-wait job when job_id is omitted.

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

Input Schema

NameRequiredDescriptionDefault
job_idNoJob to run; omit to run the next due queued or retry_wait job.
worker_idNoOptional identifier recorded as the worker that ran the job.
queue_rootYesDirectory holding the filesystem job queue; created if missing.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.3.13
    • addedInput schema / properties / job_id / description
      Added value: +"Job to run; omit to run the next due queued or retry_wait job."
    • addedInput schema / properties / queue_root / description
      Added value: +"Directory holding the filesystem job queue; created if missing."
    • addedInput schema / properties / worker_id / description
      Added value: +"Optional identifier recorded as the worker that ran the job."
  2. First observedv0.3.12

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare the important traits (not read-only, not idempotent, open-world, non-destructive), so the description does not need to restate them. It usefully adds that retry_wait jobs are eligible for automatic pickup, but says nothing about what running a job actually does — state transitions, filesystem writes, or external fetches — which matters for an open-world mutation.

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

Conciseness5/5

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

A single tight sentence with the primary action front-loaded and the conditional default presented as a subordinate clause. No filler.

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

Completeness5/5

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

There is no output schema, so the description is not obligated to describe return values, and the parameter schema is fully documented. For a three-parameter queue-runner, the definition gives an agent enough to invoke it correctly in either mode.

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%, so all three parameters are already documented. The description reinforces the job_id omission semantics but adds no syntax, format, or constraints (e.g., what constitutes 'due', or how queue_root interacts with worker_id) beyond the schema.

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 ('Run one clone queue job') and clarifies the default selection behavior when job_id is omitted. It is distinguishable from siblings like enqueue_clone_job and cancel_clone_job, though it never names them explicitly.

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?

The sentence implies two usage modes: target a specific job, or let the tool pull the next due queued/retry_wait job. What is missing is guidance on when to prefer this over enqueue/list/load siblings, and whether it should be looped until the queue drains.

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