Skip to main content
Glama

Search Social Drafts Tool

search-social-drafts
Read-only

Searches authorized social drafts and returns bounded content, status, platform, source-review, and approval metadata. Use to search social drafts in the connected business. Returns query, count, total, drafts, resolution, scope.

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": "search-social-drafts"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of drafts to return.
queryNoDraft content, platform, status, or ID.
statusNoDraft approval state.
platformNoSocial platform.
review_idNoOptional source review ID.

Output Schema

NameRequiredDescriptionDefault
countYesCount for the returned result.
queryYesQuery used or returned by this tool.
scopeYesAuthorization scope of this result; data remains restricted to the connected business.
totalYesTotal for the returned result.
draftsYesBounded drafts records returned by this tool.
resolutionYesSearch match resolution: exact, single, broad, or ambiguous.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "count": {
      +      "description": "Count for the returned result.",
      +      "type": "integer"
      +    },
      +    "drafts": {
      +      "description": "Bounded drafts records returned by this tool.",
      +      "items": {
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "query": {
      +      "description": "Query used or returned by this tool.",
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "resolution": {
      +      "description": "Search match resolution: exact, single, broad, or ambiguous.",
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "scope": {
      +      "description": "Authorization scope of this result; data remains restricted to the connected business.",
      +      "enum": [
      +        "connection_business"
      +      ],
      +      "type": "string"
      +    },
      +    "total": {
      +      "description": "Total for the returned result.",
      +      "type": "integer"
      +    }
      +  },
      +  "required": [
      +    "query",
      +    "count",
      +    "total",
      +    "drafts",
      +    "resolution",
      +    "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?

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds a modest scoping claim ("authorized" drafts, "in the connected business") and says results are "bounded", but does not state the bound, ordering, or what happens when no filters match. Useful but thin on top of annotations.

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

Conciseness3/5

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

The purpose claim is front-loaded, which is good, but the second sentence is pure redundancy and the third enumerates return keys already covered by the output schema. Two of three sentences do little work.

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?

With an output schema present, full annotation coverage, and 100% schema description coverage, the description only needs to convey scope, which it does (authorized drafts in the connected business). The remaining gap is routing guidance against sibling search tools, which is not strictly required for correct invocation.

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%, with all five parameters documented including two enums, so the schema carries parameter meaning. The description only echoes the query/status/platform concepts already present and adds no syntax, matching behavior, or interplay between filters, leaving the baseline score.

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 ("Searches authorized social drafts") and names the field families returned, so the agent knows this is a read over draft records rather than reviews or campaigns. It does not explicitly name a sibling to contrast with (e.g. preview-social-draft or search-reviews), so it stops short of full differentiation.

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?

"Use to search social drafts in the connected business" merely restates the purpose sentence and adds no condition, prerequisite, or exclusion. Nothing tells the agent when to prefer this over preview-social-draft or search-reviews, and no guidance on empty-query behavior is given.

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