Skip to main content
Glama

Is WoopSocial publishing ready

woopsocial_status

Verifies whether Clips Kitty can publish to social platforms through your WoopSocial account, so check it before offering to schedule posts.

Instructions

Whether Clips Kitty can post to social platforms through the person's WoopSocial account. Check this before offering to schedule anything.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior3/5

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

No annotations and no output schema are supplied, so the description carries the full disclosure burden. It implies a boolean readiness result and implies a non-mutating check, but it does not describe what is returned when the account is not connected, whether any auth or configuration state is reported, or whether the call has side effects such as triggering a token refresh.

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 with no filler: the first states the condition being checked, the second states the action to take based on it. Purpose is front-loaded and every sentence earns its place.

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

Completeness4/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 output schema, the description gives enough to select and call it correctly. The remaining gap is what a negative result means operationally (account not linked, needs re-auth) and what the caller should do next, which matters more here because no output schema documents the response.

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 beyond the schema. Baseline 4 applies; no parameter-related omissions exist.

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 names the specific resource and condition: whether Clips Kitty can post to social platforms via the person's WoopSocial account, i.e. a readiness/connectivity check. That is clearly a read-only status probe, but it does not differentiate itself from sibling status tools such as uploadpost_status, youtube_status, or publish_status, so an agent must infer which status tool answers which question.

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?

The second sentence gives explicit, actionable timing guidance: "Check this before offering to schedule anything," which frames the tool as a precondition gate for scheduling. It stops short of naming alternatives or stating when the check can be skipped, but the primary usage context is unambiguous.

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