Skip to main content
Glama
Content Drifter MCP

Content Drifter MCP

Official
by OPTRIXTECH

list_upcoming_posts

Retrieve upcoming scheduled or draft social posts, with optional platform and ISO date-range filters to review and plan content.

Instructions

List upcoming scheduled or draft posts. Optional platform filter and date range (ISO from/to).

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

Input Schema

NameRequiredDescriptionDefault
toNoISO datetime upper bound
fromNoISO datetime lower bound
platformNoOptional network filter. twitter is X.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

B3.2/5.0
Behavior2/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 does disclose that both scheduled and draft posts are included, which is useful scope information, but it says nothing about ordering, pagination, result limits, or whether drafts and scheduled items are distinguishable in the output.

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, front-loaded with the core purpose and followed by the filter capabilities. The '(ISO from/to)' parenthetical is mildly redundant with the schema but otherwise there is no wasted wording.

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 simple read-only listing tool with three optional parameters and no output schema, the description covers the essentials of what is returned at a high level. It stops short of describing result shape, ordering, or volume, which an agent would want given no output schema exists to fill that gap.

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 the schema already documents all three parameters including the ISO bounds and the enum values. The description restates the ISO from/to semantics and the platform filter without adding format details, defaults, or interaction rules (e.g., whether from/to are inclusive).

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 gives a specific verb and resource: 'List upcoming scheduled or draft posts.' It clearly scopes results to not-yet-published items, which separates it in spirit from publish_now and schedule_post, though it never names those siblings explicitly.

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?

Mentioning the optional platform filter and date range implies the intended retrieval scenarios, but there is no explicit when-to-use guidance, no statement of when another tool (e.g., publish_now, schedule_post) is the better choice, and no prerequisites or auth notes.

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