Skip to main content
Glama
Podcast MCP
by calebn

propose_social_clips_tool

Propose short-form social clips for a platform up to a set limit; rerun keeps approved and manually added clips while replacing the rest.

Instructions

Propose short-form social clips for a platform, limited to max_clips.

A rerun keeps approved and manually added clips and replaces the rest.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "propose_social_clips_tool"
  }
}

Input Schema

NameRequiredDescriptionDefault
platformNo
max_clipsNo
project_pathNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.1.1
    • addedInput schema / properties / project_path / anyOf
      Added value: +[
      +  {
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • addedInput schema / properties / project_path / default
      Added value: +null
    • removedInput schema / properties / project_path / type
      Removed value: -"string"
    • removedInput schema / required
      Removed value: -[
      -  "project_path"
      -]
  2. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations at all, the description carries the full disclosure burden. It does add one genuinely valuable trait beyond the schema — rerun semantics that preserve approved and manually added clips while replacing the rest — which tells the agent the operation is safely repeatable. It omits, however, whether this is a write operation, what state it leaves behind before approval, and any permission or cost constraints.

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 short sentences, front-loaded with the core action and immediately followed by the one behavioral caveat that matters. No filler, no restatement of the tool name.

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

Completeness3/5

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

An output schema exists, so return values need not be described. For a three-parameter tool with zero schema documentation, though, the description leaves two parameters undefined and gives no indication of what a 'proposal' produces or how it interacts with the approve/reject flow, which is the natural next step an agent must know about.

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

Parameters2/5

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

Schema coverage is 0%, so the description must compensate for all three parameters, and it only explains one: max_clips, as the cap on generated clips. The meaning of 'platform' (which platform, allowed values) and 'project_path' (what project scope it selects) is left entirely undocumented in both schema and description.

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 gives a specific verb and resource ('Propose short-form social clips') plus a scope qualifier ('for a platform, limited to max_clips'), which is enough for an agent to distinguish it from approve/reject/list siblings. It stops short of explicitly naming those siblings or stating how the proposal relates to them.

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?

Usage is implied rather than stated: 'propose' suggests generating a candidate set for later approval, and the rerun sentence hints at iterative re-proposal. There is no explicit when-to-use versus approve_social_clips_tool or list_social_clips_tool, and no stated preconditions such as whether clips must already exist or whether a proposal requires approval.

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