Skip to main content
Glama
Sign In
publish-pilot-mcp

publish-pilot-mcp

by acus9345
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

job_status

Monitor the status and review the output of automated login and publish jobs. Specify a job ID to track progress, or run without an ID to view a complete list of ongoing tasks.

Instructions

Status and output of a login/publish job; without id, lists jobs.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "job_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNo
stopNo
sendEnterNoAnswer a 'Press ENTER' prompt
waitSecondsNoMax 45 s per call; call again while running

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.4.0
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • removedInput schema / properties / id / description
      Removed value: -"Job id from login, publish_package or setup_trusted_publishing."
    • changedInput schema / properties / sendEnter / description
      Previous value: -"Send Enter to the job (for 'Press ENTER' prompts)."New value: +"Answer a 'Press ENTER' prompt"
    • removedInput schema / properties / stop / description
      Removed value: -"Stop the job (e.g. to restart a publish whose link expired)."
    • changedInput schema / properties / waitSeconds / description
      Previous value: -"Wait up to this long for the job to finish. Capped at 45 s per call so the call returns before common 60 s client timeouts; call again while running is true."New value: +"Max 45 s per call; call again while running"
  2. Changed1 schema field changedv0.3.0
    • changedInput schema / properties / waitSeconds / description
      Previous value: -"Wait up to this long for the job to finish (keep under your client's tool timeout)."New value: +"Wait up to this long for the job to finish. Capped at 45 s per call so the call returns before common 60 s client timeouts; call again while running is true."
  3. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

Annotations only declare openWorldHint=false, so the description must carry nearly the full behavioral burden. It reveals that the tool returns output in addition to status, but says nothing about the long-polling nature (45s cap, re-call while running), what stop actually does, or whether stopping is destructive/irreversible.

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 compact clause with the listing behavior front-loaded alongside the primary purpose. It is efficient, though the terseness edges toward under-specification rather than pure conciseness.

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

Completeness2/5

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

With four parameters, no output schema, and negligible annotations, the description should explain the existing-output return and polling/stop behavior. It leaves the stop parameter and the output format completely unaddressed, which is inadequate for a job-control tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 50%; sendEnter and waitSeconds are documented in the schema, but 'stop' — the one mutating parameter — has no description in either place, and 'id' is only partially implied by the listing behavior. The description does not compensate for the undocumented stop semantics.

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 ('Status and output of a login/publish job') and clarifies the dual mode with 'without id, lists jobs'. An agent can tell it apart from the job-spawning siblings like login and publish_package, though the relationship to polling siblings such as watch_workflow is not made explicit.

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?

'without id, lists jobs' gives one implied conditional for the no-arg case, which is useful. However, there is no guidance on when to call this versus watch_workflow, or when to use stop instead of simply re-polling.

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