Skip to main content
Glama

Request a heistclips feature

request_a_feature

Files a feature request on heistclips' public board (heistclips.com/requests) and emails the person who builds it. Use when the user wants heistclips or this connector to do something it does not: a platform, a layout, captions, alerts, a campaign source. Pass their words VERBATIM as title (short) and optional detail; pass contact only if they offer an email or handle, exactly as written. Ask first if you do not know what they want. Tell them it was filed only if ok is true.

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": {
      "title": "<title>"
    },
    "name": "request_a_feature"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleYesWhat they want, in their own words, under 90 characters
detailNoOptional: what they were trying to do
contactNoOptional: email or handle for a reply, verbatim, only if offered

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations only say this is a non-read-only, open-world, non-idempotent write. The description adds material facts the agent cannot get elsewhere: the request posts to a PUBLIC board, a human is emailed, and success must be confirmed via an `ok` field before telling the user it was filed. That public-visibility disclosure is exactly the kind of behavioral context the annotations omit.

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?

Front-loaded with purpose and destination before the usage rule, with no filler sentences. It is dense—several imperative instructions packed into one paragraph—which slightly hurts scannability but nothing is redundant.

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 three-parameter, no-output-schema tool the definition covers purpose, trigger, parameter fidelity, and the success signal. The only gap is that no output schema exists and the response shape is only hinted at via `ok`, so other failure modes (e.g., duplicate filings, given non-idempotentHint) are left implicit.

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 100%, so the baseline is 3, and the description goes beyond it by instructing that the text be passed VERBATIM (title short, detail optional) and that `contact` be supplied only if offered and exactly as written. This adds a fidelity/privacy rule the schema does not state, though it partly restates the schema's 'in their own words' wording.

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 ('Files a feature request on heistclips' public board') plus the side effect ('emails the person who builds it'), and even names the destination URL. That is enough to separate it from upvote_feature_request and list_feature_requests without opening either schema.

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 an explicit trigger condition ('use when the user wants heistclips or this connector to do something it does not') with concrete examples of the kind of gap that qualifies, plus a clarification precondition ('Ask first if you do not know what they want'). It does not explicitly exclude near-miss cases such as filing a bug report, but the primary when-to-use is clear.

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.