Skip to main content
Glama

Report Publish

report_publish
Destructive

Publish report drafts or republish earlier revisions to make a chosen version visible to viewers immediately; supports dry runs and verifies the published revision by read-back.

Instructions

Publish the draft to viewers (Publish button), or republish an earlier revision (Version history > Publish this version). Only for manual publishing. Viewers see the result immediately; verified by the published revision read-back.

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

Input Schema

NameRequiredDescriptionDefault
dry_runNo
report_idNo
revision_numberNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.5

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false and destructiveHint=true, so the mutation risk is known. The description usefully adds the user-visible effect ('Viewers see the result immediately') and a verification mechanism ('verified by the published revision read-back'), but omits what republishing an earlier revision does to the current live state (an effective rollback) and how dry_run changes behavior.

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?

The operation and its scoping constraint are front-loaded in the first clause, and the UI-path parentheticals aid recognition rather than padding. Slightly long for the information delivered, but no sentence is wasted.

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?

An output schema exists, so return values need no explanation. However, for a destructive, zero-required-parameter publishing tool with fully undocumented parameters, the description should clarify what report_id defaults to, what dry_run=true means in practice, and the consequence of republishing an older revision; those gaps matter for correct invocation.

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 description coverage is 0% across three parameters, so the description bears the full burden, yet it explains none of them directly. 'republish an earlier revision' gestures at revision_number and 'the draft' implies report_id, but the dry_run flag — which defaults to true and determines whether anything actually goes live — is never mentioned, leaving the most consequential parameter undocumented.

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?

The description names a specific verb and resource ('Publish the draft', 'republish an earlier revision') and distinguishes two concrete publishing paths via UI affordances. It is clear what operation is performed, though it does not name any sibling tool by name (e.g. report_publishing_mode) to sharpen the boundary.

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?

'Only for manual publishing' gives a clear selection condition against non-manual (presumably scheduled/automated) publishing, which is a real fork in this tool family. It stops short of naming the alternative tool explicitly or stating exclusions such as when a draft has no changes.

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