Skip to main content
Glama

Listing copy worksheet

toolfound_listing_copy
Read-onlyIdempotent

Turn supplied product facts into deterministic, editable listing copy without inventing claims. Returns an evidence-bounded result and the canonical web tool URL.

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": {
      "name": "<name>",
      "audience": "<audience>",
      "problem": "<problem>",
      "outcome": "<outcome>"
    },
    "name": "toolfound_listing_copy"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesYour product's public name.
outcomeYesThe specific result a user gets once the problem is solved.
problemYesThe concrete problem your audience has today, in your own words. The copy is built from this text and does not add claims.
audienceYesWho the product is for, as a short phrase such as independent design teams.
differentiatorNoOptional: what your approach does differently from existing options. Only stated facts are used.

Output Schema

NameRequiredDescriptionDefault
okYes
dataNo
linksYes
errorsNo
summaryYes
sectionsYes
canonical_result_urlYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedInput schema / properties / audience / description
      Added value: +"Who the product is for, as a short phrase such as independent design teams."
    • addedInput schema / properties / differentiator / description
      Added value: +"Optional: what your approach does differently from existing options. Only stated facts are used."
    • addedInput schema / properties / name / description
      Added value: +"Your product's public name."
    • addedInput schema / properties / outcome / description
      Added value: +"The specific result a user gets once the problem is solved."
    • addedInput schema / properties / problem / description
      Added value: +"The concrete problem your audience has today, in your own words. The copy is built from this text and does not add claims."
  2. Added

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the description's job is to add context — and it does: 'deterministic', 'evidence-bounded result', 'does not invent claims', and the note that a canonical web tool URL is returned. This is genuinely useful beyond the structured hints, and nothing contradicts them.

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?

Two tight sentences with zero filler, leading with the core transformation and then the return shape. The no-invented-claims constraint is front-loaded where it matters most.

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?

With a full output schema and rich annotations, the description needn't explain return values, and it still flags the evidence-bounded output and canonical URL. What's missing is how this differs from sibling listing/claim tools, which is the only real gap for a read-only generator.

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 description coverage is 100%, so each of the five parameters is already documented, including that 'problem' text drives the copy. The description only restates the facts-in/copy-out relationship without adding format, tone, or length guidance for the inputs, so the baseline 3 applies.

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 artifact — 'turn supplied product facts into ... listing copy' — plus a defining constraint ('without inventing claims'). That clearly separates it from a generic copywriter, though it does not explicitly distinguish it from the similarly named sibling toolfound_claim_listing.

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

Usage Guidelines2/5

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

There is no explicit when-to-use or when-not-to-use guidance and no alternative is named. The phrase 'supplied product facts' weakly implies the prerequisite of having facts on hand, but an agent gets no routing signal versus sibling tools such as toolfound_claim_listing or toolfound_launch_review.

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