Skip to main content
Glama
dinwal

RecurPost MCP Server

by dinwal
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

history_data

Get posting history for a social account (max 100 posts per request), with optional date range and video update metrics, to analyze past content performance.

Instructions

Get posting history for a social account (max 100 posts per request)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesSocial account ID (from social_account_list)
end_dateNoEnd date in YYYY-MM-DD HH:MM:SS format
start_dateNoStart date in YYYY-MM-DD HH:MM:SS format
workspace_idNoWorkspace ID (ws_id from workspace_list). Omit to use your default workspace.
is_get_video_updatesNoInclude video update metrics (default: true)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.1.3
    • addedInput schema / properties / workspace_id
      Added value: +{
+  "description": "Workspace ID (ws_id from workspace_list). Omit to use your default workspace.",
+  "type": "string"
+}
  2. First observedv1.0.0

TDQS

A3.5/5.0
Behavior2/5

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

Since no annotations are provided, the description carries the full behavioral burden. It does disclose a rate/limit constraint ('max 100 posts per request'), but it does not mention pagination, response shape, error behavior, or authentication requirements. This is too thin for a tool with zero annotation support.

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?

The description is a single front-loaded sentence that states the action, target, and key constraint without filler. Every part earns 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?

The schema covers parameter semantics well, and the core purpose is clear. However, with no output schema and no annotations, the description does not explain the return structure, how to fetch beyond 100 posts, or how date-range and video-update flags affect the result. These are meaningful gaps for a history-retrieval tool.

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?

All five parameters are documented in the schema, including source hints ('from social_account_list'), date formats, and defaults. The free-text description adds no parameter-level meaning beyond the schema, so the baseline of 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?

The description uses a specific verb ('Get') and resource ('posting history for a social account'), making the tool's function clear. It also adds a concrete limit ('max 100 posts per request'), but it does not explicitly differentiate from sibling tools, though none obviously overlaps.

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 description clearly implies when to use the tool: when posting history for a social account is needed. It does not state exclusions or name alternatives, but among the listed siblings, none appears to provide the same history-retrieval function.

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

Deploy Server

Other Tools