Skip to main content
Glama

Validate Caption

reelsfarm_validate_caption
Read-onlyIdempotent

Check caption length and hashtag counts against ReelsFarm platform publishing rules.

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": {
      "caption": "<caption>",
      "platforms": "<platforms>"
    },
    "name": "reelsfarm_validate_caption"
  }
}

Input Schema

NameRequiredDescriptionDefault
captionYesCaption text. Omit it for no caption.
platformsYesOne or more social platforms used for validation or publishing.

Output Schema

NameRequiredDescriptionDefault
validNo
platformsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changed
    • removedInput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
    • changedInput schema / properties / caption / description
      Previous value: -"Social caption or video-part caption text. Omit it when no caption is required."New value: +"Caption text. Omit it for no caption."
    • removedOutput schema / $defs
      Removed value: -{
      -  "__schema0": {
      -    "anyOf": [
      -      {
      -        "type": "string"
      -      },
      -      {
      -        "type": "number"
      -      },
      -      {
      -        "type": "boolean"
      -      },
      -      {
      -        "type": "null"
      -      },
      -      {
      -        "items": {
      -          "$ref": "#/$defs/__schema0"
      -        },
      -        "type": "array"
      -      },
      -      {
      -        "additionalProperties": {
      -          "$ref": "#/$defs/__schema0"
      -        },
      -        "propertyNames": {
      -          "type": "string"
      -        },
      -        "type": "object"
      -      }
      -    ]
      -  },
      -  "__schema1": {
      -    "anyOf": [
      -      {
      -        "type": "string"
      -      },
      -      {
      -        "type": "number"
      -      },
      -      {
      -        "type": "boolean"
      -      },
      -      {
      -        "type": "null"
      -      },
      -      {
      -        "items": {
      -          "$ref": "#/$defs/__schema1"
      -        },
      -        "type": "array"
      -      },
      -      {
      -        "additionalProperties": {
      -          "$ref": "#/$defs/__schema1"
      -        },
      -        "propertyNames": {
      -          "type": "string"
      -        },
      -        "type": "object"
      -      }
      -    ]
      -  }
      -}
    • removedOutput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
    • removedOutput schema / properties / platforms / $ref
      Removed value: -"#/$defs/__schema1"
    • removedOutput schema / properties / platforms / description
      Removed value: -"Structured platforms value returned by reelsfarm_validate_caption."
    • removedOutput schema / properties / valid / $ref
      Removed value: -"#/$defs/__schema0"
    • removedOutput schema / properties / valid / description
      Removed value: -"Structured valid value returned by reelsfarm_validate_caption."
  2. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and closed-world, so the safety profile is covered. The description adds that validation is against per-platform publishing rules rather than a generic length check, but says nothing about what a failed validation implies or whether it blocks later publish calls.

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?

A single sentence with no filler, and the object of the check is front-loaded. Nothing is repeated from the title or schema.

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?

An output schema exists and annotations cover the safety profile, so the description only needs to frame the purpose, which it does. It falls slightly short on the multi-platform semantics — with an array of platforms accepted, an agent cannot tell whether results are aggregated or per-platform.

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%, so both the caption string and the platforms enum array are documented in the schema itself. The description's mention of 'caption length and hashtag counts' loosely maps to the caption param but adds no per-platform rule detail (e.g. whether the strictest platform wins) beyond the schema.

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?

States a concrete verb and resource ('Check caption length and hashtag counts') scoped to ReelsFarm platform publishing rules, which is specific enough to identify the operation. It does not, however, distinguish itself from the nearby sibling reelsfarm_preflight_publishing, which is the most likely confusion point.

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?

Usage is only implied — an agent can guess this is a pre-publish check, but the description never says when to call it versus preflight_publishing or confirm_publish_now. No prerequisites, no when-not conditions, no mention of whether validation is a hard gate for publishing.

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.

Resources