Skip to main content
Glama

Show a built page on the board

inspo_add_build

Publish a page build (HTML, file, or URL) to the board's Page tab so users vote and comment section by section; mark section roots with data-inspo.

Instructions

Publish a version of the page you built (v1, v2…) to the board's Page tab, where the user votes and comments section by section and can click anywhere to leave a note. Pass html (a standalone document) or file (absolute path to an .html file; its folder is served so relative assets work) or url (e.g. a running dev server; no click-comments then). Mark every section root with data-inspo="" (e.g. ) so feedback maps to sections.

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

Input Schema

NameRequiredDescriptionDefault
urlNo
fileNo
htmlNo
labelNoWhat changed in this version, one line.
notesNo
sessionNoSession id. Defaults to the most recent session in this project.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

A4.4/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the burden and does well: it explains the user-facing effect (board Page tab, voting and commenting per section, click-anywhere notes), a functional limitation of url mode, and the hard requirement that every section root carry data-inspo. It does not say whether republishing replaces the prior version, whether auth is required, or what the call returns, which are meaningful gaps for a publish/mutation operation.

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?

Three sentences, front-loaded with what publishing does before the input modes and then the data-inspo contract. The parentheticals carry real information (example attribute value, dev-server case, asset-serving behavior) rather than waste.

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 six-parameter publish tool with no annotations and no output schema, the description covers the risky parts: input mode distinctions, the section-markup contract that makes feedback work, and the url-mode limitation. It remains silent on versioning semantics, auth, and return values, but everything an agent needs to invoke the tool correctly for the primary paths is present.

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 only 33%, so the description must compensate, and it substantially does: html is described as a standalone document, file as an absolute path whose folder is served (explaining why relative assets work), and url as a running dev server with the click-comment caveat. The label parameter is only covered by the schema and notes is undocumented anywhere, leaving two of six parameters without semantic guidance.

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 precise verb and resource — publishing a built page version (v1, v2…) to the board's Page tab — and describes the resulting artifact and its use (section-by-section voting/comments). It is clearly distinguishable from sibling tools like inspo_add_component or inspo_export_pdf.

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?

Gives explicit mode-selection guidance: pass html, file, or url, with the tradeoff that url input loses click-comments and file input serves the containing folder so relative assets resolve. It stops short of naming when to prefer a sibling tool (e.g. inspo_review or inspo_next_round) or stating prerequisites, so it is clear context without full alternatives.

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