Skip to main content
Glama

generate_appeal

Read-only

Generate a ready-to-submit appeal response for a TikTok, Amazon, or YouTube policy violation notice. Stays within TikTok's 800-character appeal limit. Paste the violation notice text you received and specify the platform.

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": {
      "violation_notice": "<violation_notice>",
      "platform": "<platform>"
    },
    "name": "generate_appeal"
  }
}

Input Schema

NameRequiredDescriptionDefault
platformYesThe platform that issued the violation: tiktok, amazon, or youtube.
violation_noticeYesThe full text of the violation notice or strike you received from the platform.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / additionalProperties
      Removed value: -false
  2. Added

TDQS

A4.3/5.0
Behavior4/5

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

Beyond the read-only and non-destructive annotations, it discloses that the result is ready to submit and must stay within TikTok's 800-character appeal limit. It does not provide comparable output constraints for Amazon or YouTube.

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?

The purpose is front-loaded, followed by a concrete output constraint and brief invocation instructions. All three sentences are useful, with no filler or redundancy.

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?

For a simple two-parameter tool, the definition covers the task, supported platforms, required inputs, and an important output limitation. Despite the absence of an output schema, an agent has enough context to select and invoke it correctly.

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 both parameters are already clearly documented, including the platform enum. The description reinforces how to supply them but adds no parameter meaning beyond the schema.

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 output—generating a ready-to-submit appeal response—and identifies both the triggering resource and supported platforms. This clearly distinguishes it from the sibling audit_script tool.

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?

It tells the agent to use the tool after receiving a policy violation notice and instructs it to paste that notice and specify the platform. It provides clear usage context, though no explicit when-not guidance or alternative tool.

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.