Skip to main content
Glama

Publish a monitor as a public tracker

publish_tracker

Publishes a previewed monitor revision as a public tracker people can follow, optionally adding it to an existing tracker or starting a multi-source tracker, and returns the shareable address.

Instructions

Step 2 of 2 (needs a network:publish key): publish exactly what create_public_tracker or preview_network_watch showed (its revisionId) as a public tracker people can follow. On its own it is a tracker with one source, its own page; with trackerRef or trackerTitle it also joins one of the person's trackers with several sources, or starts one. Returns the address to share. Publishing cannot be undone for anyone who saw it; the person can withdraw it later.

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": {
      "monitorUuid": "<monitorUuid>",
      "revisionId": "<revisionId>"
    },
    "name": "publish_tracker"
  }
}

Input Schema

NameRequiredDescriptionDefault
revisionIdYesrevisionId from create_public_tracker or preview_network_watch
trackerRefNoOne of your trackers with several sources to add it to; leave out, with trackerTitle, for a tracker of its own
monitorUuidYesThe same monitor
trackerTitleNoStart a new tracker with several sources, with this one first; leave out for a tracker of its own
trackerDescriptionNoWhat the new tracker is for, for people deciding to follow it

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

A4.6/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does: it discloses the network:publish authorization requirement, the irreversible visibility consequence ('cannot be undone for anyone who saw it'), the mitigation ('the person can withdraw it later'), and the return value ('the address to share'). That is exactly the context an agent needs before a publishing mutation.

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?

Three sentences, front-loaded with the step-2 framing and the required key, then mode behavior, then consequences and return value — every sentence carries information. The middle sentence is heavily nested ('with trackerRef or trackerTitle it also joins...or starts one') and could be split for faster parsing.

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?

No output schema exists, yet the description still says what comes back (the shareable address). For a 5-parameter irreversible mutation with no annotations, it covers prerequisites, mode selection, side effects, and undo path — nothing material is missing for a correct invocation.

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

Parameters4/5

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

Schema coverage is 100%, so the per-parameter baseline is 3; the description adds cross-parameter meaning by explaining the default behavior without trackerRef/trackerTitle (a one-source tracker with its own page) versus the joined/new multi-source tracker case. It reinforces the schema rather than duplicating it verbatim, though it does not clarify revisionId scoping beyond what the schema states.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Specific verb and resource: publishes a previously previewed revision (by revisionId) as a followable public tracker, and names create_public_tracker and preview_network_watch as the step-1 producers of that revisionId. The two operating modes (standalone tracker vs. joining/starting a multi-source tracker) are stated explicitly, so an agent can distinguish this from the sibling creation/preview tools.

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?

'Step 2 of 2 (needs a network:publish key)' plus the revisionId requirement gives a clear precondition chain and points at the exact prior tools. It also explains when to pass trackerRef/trackerTitle versus omitting them. The one gap is that it never states when to prefer the sibling publish_network_watch over this tool.

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