Skip to main content
Glama

Submit by Hand

Draft listing copy for a product

draft_listing
Read-only

Read a product's website and draft the listing copy directories ask for (name, tagline, short and long descriptions, categories, tags, features, use cases), then count how many directories in our list fit the product. Also returns each plan next to what the same directories take by hand (accounts to create, email confirmations, captchas, estimated hours), so the user can compare. Free; takes 10-30 seconds. The returned preview_id can be passed to create_order.

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": {
      "url": "<url>"
    },
    "name": "draft_listing"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesThe product website, like yourproduct.com.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations only declare readOnlyHint and openWorldHint; the description adds genuinely new context — that an external website is fetched and parsed, that the call is free, that it blocks for 10-30 seconds, what content comes back (copy, fit counts, manual-effort comparison per plan), and that it emits a preview_id for downstream use. It stays consistent with the read-only/open-world annotations rather than contradicting them. It stops short of covering failure modes, e.g. what happens if the URL is unreachable or unscrapeable.

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 action and its outputs are front-loaded in the first sentence, with cost/latency and the create_order handoff following in short clauses. It is a dense single paragraph that could be split into output-contents versus timing bullets, but no sentence is filler.

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

Completeness5/5

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

With no output schema, the description takes on the burden of describing returns and does so thoroughly: the drafted copy fields, the count of fitting directories, the per-plan manual-effort comparison, and the preview_id. An agent can predict both what it gets back and how to use it without opening a schema.

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?

There is a single parameter and the schema already documents it at 100% coverage ('The product website, like yourproduct.com'). The description only indirectly adds that the URL must be a live, publicly readable product site that will be read and summarized, which is a modest clarification rather than new detail. Baseline 3 is appropriate when the schema carries the load.

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?

The description names a specific verb and resource — read a product website, draft listing copy (with the exact fields: name, tagline, short/long descriptions, categories, tags, features, use cases), then count matching directories and return a manual-effort comparison. That is far more than a restatement of the name, and it clearly separates this from create_order and search_directories.

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?

The chaining guidance is explicit: 'The returned preview_id can be passed to create_order', which tells the agent exactly where this tool sits in the workflow. It also signals cost and runtime ('Free; takes 10-30 seconds'), helping the agent decide to call it. What's missing is any stated exclusion — e.g. when to skip drafting and go straight to an existing order or directory lookup.

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