Skip to main content
Glama
dinwal

RecurPost MCP Server

by dinwal
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Local

history_data

Retrieve social media posting history for an account, including up to 100 posts within specified date ranges, with optional video metrics.

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)
start_dateNoStart date in YYYY-MM-DD HH:MM:SS format
end_dateNoEnd date in YYYY-MM-DD HH:MM:SS format
is_get_video_updatesNoInclude video update metrics (default: true)

Implementation Reference

  • src/index.ts:113-138 (handler)
    The 'history_data' tool definition and handler implementation. It uses the `callAPI` helper to fetch posting history from RecurPost with optional date filtering and video metric settings.
    server.tool(
  "history_data",
  "Get posting history for a social account (max 100 posts per request)",
  {
    id: z.string().describe("Social account ID (from social_account_list)"),
    start_date: z
      .string()
      .optional()
      .describe("Start date in YYYY-MM-DD HH:MM:SS format"),
    end_date: z
      .string()
      .optional()
      .describe("End date in YYYY-MM-DD HH:MM:SS format"),
    is_get_video_updates: z
      .boolean()
      .optional()
      .describe("Include video update metrics (default: true)"),
  },
  async (params) => {
    try {
      return toolResult(await callAPI("/api/history_data", params));
    } catch (e) {
      return toolResult({ error: String(e) }, true);
    }
  }
);

Tool Definition Quality

A3.7/5.0
Behavior3/5

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

No annotations provided, so description carries full disclosure burden. It successfully communicates the 100-post limit constraint (critical for pagination planning). However, lacks safety profile (read-only implied but not stated), error conditions, and return value structure given no 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.

Conciseness5/5

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

Extremely efficient single sentence of 11 words. Front-loaded with action 'Get posting history', followed by target scope, ending with critical constraint. No repetition, tautology, or filler.

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?

Adequate for a 4-parameter read tool: mentions key constraint (100 posts). However, with no output schema provided, description should ideally characterize return data structure (post objects, metrics, etc.) which is absent. Missing behavioral details like date range defaults when optional params omitted.

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% (all 4 parameters well-documented). Description does not explicitly document parameters but mentions the 100-post constraint which contextualizes the id parameter's purpose. Baseline 3 appropriate since schema does heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Clear specific verb 'Get' + resource 'posting history' + scope 'social account'. The parenthetical '(max 100 posts per request)' clarifies volume constraints. Distinguishes from siblings like post_content (creates), social_account_list (lists accounts), and library_list (lists library items) by targeting retrieved historical post data.

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?

Implied usage is clear (retrieve historical posts), but lacks explicit 'when to use' guidance, prerequisites, or named alternatives. The max 100 posts constraint provides implicit usage guidance regarding pagination needs, preventing a lower score.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/dinwal/recurpost-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server