Skip to main content
Glama

Is multi-platform publishing ready

uploadpost_status

Checks whether Clips Kitty can publish clips to multiple platforms through your Upload-Post account and which profile to use; verify this before offering posts outside YouTube.

Instructions

Whether Clips Kitty can publish to several platforms at once through the user's Upload-Post account, and which profile. Check this before offering to publish anywhere other than YouTube.

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": "uploadpost_status"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It implies a read-only capability probe and hints at the return content ('whether ... can publish' and 'which profile'), but it never states what happens when publishing is not ready, whether this is a cached or live check, or what authorization the account needs.

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?

Two short sentences with no wasted preamble; the readiness question comes first and the usage instruction second. The phrase 'through the user's Upload-Post account' and 'which profile' are slightly compressed and could be read as two separate questions rather than one.

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?

For a zero-parameter status tool with no annotations and no output schema, the definition should clarify what 'ready' means (connected platforms, credentials, plan limits) and what to do on failure. It covers intent and timing but leaves the interpretation of the result and the failure path underspecified.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; the baseline for a parameterless tool applies. The description correctly implies no inputs are needed, since the check is against the user's existing Upload-Post account.

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 states a specific capability check: whether the Upload-Post account can publish to multiple platforms at once, and which profile is in use. It is clearly a readiness/status query rather than a publish action, though the verb is implicit ('Whether ... can') and the product name 'Clips Kitty' adds noise without adding discriminating detail.

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 gives explicit when-to-use guidance: 'Check this before offering to publish anywhere other than YouTube,' which also implicitly excludes the YouTube-only path. It does not name the sibling that performs the actual publishing (uploadpost_publish) or state what to do when the check fails, so the routing is clear but not fully closed.

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