Skip to main content
Glama

Preview the draft

help_center_preview
Read-onlyIdempotent

A private link to any page of the DRAFT (works before the help center is public, never indexed), and the page’s HTML if you ask for it, so you can check your work. Free.

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

Input Schema

NameRequiredDescriptionDefault
htmlNo
pageNohome
queryNoFor page "search".
articleNoArticle id or slug, for page "article".
collectionNoFor page "collection".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), and the description adds meaningful context: it is private, never indexed, and works pre-publication. This is genuine value beyond the structured fields, though it doesn't explain the link's lifetime or the return shape in detail.

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 dense sentence that front-loads the core output (private draft link) and appends the conditional HTML behavior. Slightly run-on but every clause carries information.

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 read-only preview tool with full annotations and no output schema, the description covers what is returned (link + optional HTML) and the draft/non-indexed nature. It is nearly complete, only lacking finer guidance on parameter combinations.

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

Parameters3/5

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

Schema coverage is 60%, with descriptions on query, article, and collection. The description clarifies the html flag ('the page's HTML if you ask for it') but doesn't explain how page selection interacts with article/collection/query beyond what the schema already 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?

States a specific verb and resource: returns a private link to any page of the DRAFT, optionally with HTML. It clearly distinguishes itself from publish/set_public siblings by emphasizing draft, pre-public, never-indexed preview content.

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?

'So you can check your work' and 'works before the help center is public' imply the use case (verifying draft pages before publishing). However, it names no explicit alternatives (e.g. help_center_publish for going live) and gives no when-not guidance.

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