Skip to main content
Glama
Sign In

agent-media-toolkit

by io.github.krakonjac300-pixel
OverviewDiscussionsAdmin

package_post

Platform-optimized title, description, and hashtags for a clip. Premium (via x402).

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": {
      "transcript_excerpt": "<transcript_excerpt>"
    },
    "name": "package_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
nicheNo
platformsNo
transcript_excerptYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.4/5.0
Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. It mentions 'Premium' but does not explain what that entails (e.g., rate limits, authentication, or non-read-only nature). The tool likely generates data, but the description does not clarify if it is destructive or has side effects.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is very short (two sentences) and front-loaded with the key purpose, but it omits essential details about parameters and usage. It is concise but at the cost of completeness.

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

Completeness2/5

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

Given no output schema and minimal parameter documentation, the description fails to provide a complete picture. It does not specify what the tool returns or how to interpret the generated content.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, and the description does not explain any of the three parameters (transcript_excerpt, niche, platforms). It only mentions 'transcript_excerpt' implicitly via the tool name and description, leaving the user guessing about niche and platforms.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly indicates the tool generates platform-optimized metadata (title, description, hashtags) for a clip, distinguishing it from sibling tools like 'repurpose' or 'summarize' by focusing on packaging for social platforms. However, it lacks an explicit verb and could be more specific about the output.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives like 'repurpose' or 'script'. The mention of 'Premium (via x402)' hints at cost but does not provide clear context or exclusions for usage.

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

All agent-media-toolkit toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources