Skip to main content
Glama
Sign In
webEmbedding

webEmbedding

by jongko54
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

load_clone_job

Read-onlyIdempotent

Retrieve a persisted website cloning job by ID from the filesystem queue to inspect its stored status and details.

Instructions

Load one persisted clone job by id.

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

Input Schema

NameRequiredDescriptionDefault
job_idYesJob id returned by enqueue_clone_job.
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 / job_id / description
      Added value: +"Job id returned by enqueue_clone_job."
    • addedInput schema / properties / queue_root / description
      Added value: +"Directory holding the filesystem job queue; created if missing."
  2. First observedv0.3.12

TDQS

B3.3/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 only the word "persisted," which hints that state lives in the filesystem queue, but it says nothing about what happens for an unknown or expired job id (error vs empty result) or what state information is returned.

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 eight-word sentence with no filler, and the key qualifiers (one, persisted, by id) are front-loaded. Nothing 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, closed-world lookup with no output schema, the definition is minimally viable. It omits the return shape (job record/status fields) and the failure mode for a missing job id, both of which an agent would need to use the result correctly.

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 100%: job_id is documented as the value returned by enqueue_clone_job and queue_root as the queue directory created if missing. The description adds nothing beyond "by id," so the baseline 3 applies.

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?

"Load one persisted clone job by id" gives a specific verb (load) and resource (a single clone job) plus the selector (id). This distinguishes it implicitly from list_clone_jobs (many) and enqueue/run/cancel_clone_job (mutations), though it never names those siblings explicitly.

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?

There is no explicit when-to-use or when-not-to-use guidance and no alternatives named. An agent can infer this means "read a job's persisted state" and that it pairs with the id from enqueue_clone_job, but that inference comes entirely from the schema, not the description.

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