Skip to main content
Glama
Upload-Post

Upload-Post

Official

Send feedback to the Upload-Post team

send_feedback

Report an API problem, unclear tool description, or missing capability to the Upload-Post team, without credentials or post content, when no existing error message explains it.

Instructions

Tell the Upload-Post team about a problem with this API or these tools: an error you could not understand, a tool description that did not match what happened, something that looks like a bug, or a capability you needed and could not find. Use it once per problem, after you have tried to solve it; do not use it for errors the response already explains (expired connection, plan limit, payment). Describe the API, not the user's content: never include credentials, personal data or the text of the user's posts. It does not open a support ticket and gets no reply; for help with their account, the user can write to info@upload-post.com.

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": {
      "message": "<message>"
    },
    "name": "send_feedback"
  }
}

Input Schema

NameRequiredDescriptionDefault
toolNoTool (or API endpoint) the problem is about, e.g. upload_video.
agentNoWhich assistant you are, e.g. Claude, ChatGPT, Cursor.
messageYesWhat you tried, what you expected and what happened. Quote the error message if there was one.
categoryNobug: wrong behaviour. docs: a tool description or the docs were wrong or missing. error_message: an error you could not act on. feature_request: something you needed. other.
requestIdNorequest_id from the failed response, if there was one.

Output Schema

NameRequiredDescriptionDefault
resultNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.23.0

TDQS

A4.9/5.0
Behavior5/5

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

Annotations only say it is a non-read-only, non-destructive write; the description adds the consequential behavior an agent cannot infer: no support ticket is opened, no reply comes back, and the payload must exclude credentials, personal data and post text. The 'once per problem' rule also clarifies the non-idempotent hint in practical terms.

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?

Purpose comes first, then triggers, then exclusions, then privacy constraints, then what happens after sending. Dense but every clause carries a distinct rule; nothing is restated from the title or schema.

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?

Output schema covers the return value, and the description covers the remaining unknowns for a write-style reporting tool: no ticket, no reply, privacy limits, and a fallback contact route. Nothing an agent needs in order to call it correctly is missing.

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 field-level docs already exist, but the description still adds decision-relevant meaning: the message should describe the API rather than the user's content, and should quote the error. That constrains what goes into 'message' and 'tool' beyond the schema's own 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 concrete verb and recipient ('Tell the Upload-Post team') and enumerates the resource class it covers (API errors, mismatched tool descriptions, bugs, missing capabilities). No sibling tool overlaps, so an agent can identify it immediately.

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

Usage Guidelines5/5

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

Gives explicit when-to-use triggers, explicit exclusions ('do not use it for errors the response already explains (expired connection, plan limit, payment)'), a pre-condition ('after you have tried to solve it'), a frequency rule ('once per problem'), and an alternative channel ('info@upload-post.com') for account help.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools