Skip to main content
Glama

PitchWall product

run_pitchwall_products
Read-onlyIdempotent

Get one product from PitchWall by slug or URL: tagline, full description with pricing and FAQs, website, topics, publish date, social accounts, screenshots and submitter. Flat 5 points per successful run.

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": {
      "product": "<product>"
    },
    "name": "run_pitchwall_products"
  }
}

Input Schema

NameRequiredDescriptionDefault
productYesProduct slug or PitchWall URL. e.g. mainbrella-cloud-workspaces-for-ai-agents

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover readOnly, idempotent, non-destructive and openWorld behavior, so the safety profile is handled. The description adds a behavior not present in the annotations: 'Flat 5 points per successful run', a cost model an agent can use for budgeting. It does not describe not-found or error behavior, which keeps it short of a 5.

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 sentences: the first front-loads the action, identifier format and payload contents; the second states the cost. Nothing is redundant and the critical scoping information appears first.

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 no output schema, the description compensates by listing the fields returned, and the single 100%-covered parameter plus rich annotations leave little else an agent needs. Only minor gaps remain, such as behavior when the slug is invalid or not found.

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% and there is only one parameter, so the schema already documents that 'product' accepts a slug or PitchWall URL. The description repeats the same 'slug or URL' phrase without adding format, encoding, or example detail beyond the schema's inline example, so the baseline 3 is appropriate.

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 uses a specific verb and resource ('Get one product from PitchWall') and scopes it to a single item via slug or URL, which contrasts cleanly with the multi-result sibling run_pitchwall_products_search. It then enumerates the returned fields (tagline, description, pricing, FAQs, website, topics, etc.), making the tool's output concrete rather than abstract.

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?

The phrase 'by slug or URL' implicitly conveys the precondition that an identifier is required, which hints at when this tool applies versus a search. However, it never names run_pitchwall_products_search as the alternative or states when to prefer one over the other, so the guidance remains inferred rather than explicit.

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