Skip to main content
Glama

co.build

Publish approved feedback

publish_feedback
DestructiveIdempotent

Post the saved feedback preview under the connected user's public cobuild account. The mod's maintainer is notified as for a comment on the website. Requires explicit approval of the exact action and public text. Pass the draftId from prepare_feedback, its unchanged digest and consentVersion (agent-feedback-v1), and approved:true only after that approval. OAuth consent is not approval. Retrying the same draftId never posts twice. An expired draft needs a new preview and approval. Never open GitHub issues or pull requests for feedback.

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": {
      "draftId": "<draftId>",
      "digest": "<digest>",
      "consentVersion": "<consentVersion>",
      "approved": "<approved>"
    },
    "name": "publish_feedback"
  }
}

Input Schema

NameRequiredDescriptionDefault
digestYes
draftIdYes
approvedYes
consentVersionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Goes well beyond the annotations by disclosing real-world effects: the post becomes public under the user's account and the mod's maintainer is notified. It also explains retry behavior ("Retrying the same draftId never posts twice") and expiry handling, which the idempotentHint alone does not convey. The only gap is that it says nothing about what the tool returns or how failures are surfaced.

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?

Front-loaded with the action and public consequence, then the approval gate, then the parameter handoff, then edge cases — a sensible order with no filler. Minor redundancy between "Requires explicit approval" and "approved:true only after that approval," though the second does tie the rule to a specific field.

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

Completeness4/5

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

For a destructive, open-world mutation with four required parameters and no output schema, the description covers side effects, consent semantics, idempotency, and expiry. It stops short of describing the success response or error shapes, which matters somewhat given there is no output schema.

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?

With 0% schema description coverage, the description carries the load and largely does: draftId's origin (from prepare_feedback), digest's constraint (must be unchanged), consentVersion's value, and the approval condition for approved:true. The digest's meaning is only gestured at ("its unchanged digest") rather than defined, leaving slight ambiguity.

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?

States a specific verb and resource ("Post the saved feedback preview") plus the destination ("connected user's public cobuild account"). It implicitly separates itself from prepare_feedback by referring to the saved preview and the draftId it hands off, so an agent can distinguish the two stages.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly gates usage on "explicit approval of the exact action and public text" and clarifies that OAuth consent does not count. It names the prerequisite sibling (prepare_feedback) as the source of draftId and adds a clear exclusion: "Never open GitHub issues or pull requests for feedback."

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources