Skip to main content
Glama

Preview Social Draft Tool

preview-social-draft
Read-only

Validates social post copy for an authorized source review without saving or publishing it. Use to preview social draft in the connected business. Returns draft, source_review, sends, publishes, mutates, scope.

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": {
      "content": "<content>"
    },
    "name": "preview-social-draft"
  }
}

Input Schema

NameRequiredDescriptionDefault
contentYesProposed social post content.
platformNoSocial platform.
review_idNoOptional authorized source review ID.

Output Schema

NameRequiredDescriptionDefault
draftYesDraft data returned by the authorized safe projection.
scopeYesAuthorization scope of this result; data remains restricted to the connected business.
sendsYesSends flag; previews do not perform this action.
mutatesYesMutates flag; previews do not perform this action.
publishesYesPublishes flag; previews do not perform this action.
source_reviewYesSource review metadata; empty collections retain their existing JSON array representation.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / required
      Added value: +[
      +  "content"
      +]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "draft": {
      +      "description": "Draft data returned by the authorized safe projection.",
      +      "type": "object"
      +    },
      +    "mutates": {
      +      "description": "Mutates flag; previews do not perform this action.",
      +      "enum": [
      +        false
      +      ],
      +      "type": "boolean"
      +    },
      +    "publishes": {
      +      "description": "Publishes flag; previews do not perform this action.",
      +      "enum": [
      +        false
      +      ],
      +      "type": "boolean"
      +    },
      +    "scope": {
      +      "description": "Authorization scope of this result; data remains restricted to the connected business.",
      +      "enum": [
      +        "connection_business"
      +      ],
      +      "type": "string"
      +    },
      +    "sends": {
      +      "description": "Sends flag; previews do not perform this action.",
      +      "enum": [
      +        false
      +      ],
      +      "type": "boolean"
      +    },
      +    "source_review": {
      +      "description": "Source review metadata; empty collections retain their existing JSON array representation.",
      +      "type": [
      +        "object",
      +        "array",
      +        "null"
      +      ]
      +    }
      +  },
      +  "required": [
      +    "draft",
      +    "source_review",
      +    "sends",
      +    "publishes",
      +    "mutates",
      +    "scope"
      +  ],
      +  "type": "object"
      +}
  2. First observed

TDQS

B3.2/5.0
Behavior3/5

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

The description reinforces the annotations by saying it does not save or publish, which is useful confirmation but largely duplicative of readOnlyHint=true and destructiveHint=false. The trailing fragment 'Returns draft, source_review, sends, publishes, mutates, scope' is ambiguous keyword-style text that could momentarily suggest the tool sends or mutates, and it is redundant given an output schema exists.

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

Conciseness2/5

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

The first two sentences are front-loaded and efficient, but the final fragment is an ungrammatical keyword list that adds no usable meaning and dilutes an otherwise clean statement. Roughly a third of the description does not earn its place.

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?

Annotations cover the safety profile, the output schema covers return values, and all three parameters are described, so the core is adequate. What remains missing is routing guidance versus the many other preview-* and draft-related siblings, which an agent needs to choose correctly.

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 coverage is 100%, so content, platform, and review_id are already documented with types, enum, and length bounds. The description adds only the notion that review_id relates to an 'authorized source review,' which is marginal beyond the schema; baseline 3 applies.

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 specific verb and resource: 'Validates social post copy' for an 'authorized source review' with an explicit non-effect ('without saving or publishing it'). This lets an agent distinguish it from siblings like search-social-drafts or draft-review-reply, though no sibling is named directly.

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?

'Use to preview social draft in the connected business' essentially restates the tool name rather than giving a decision rule. There is no statement of when NOT to use it or which sibling to pick for adjacent tasks such as searching existing drafts or creating a review reply.

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