Skip to main content
Glama
Sign In
upload-post-mcp

upload-post-mcp

by MrSagarShah
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Edit a scheduled post

edit_scheduled_post

Update the publish time, title, or caption of a scheduled social media post using its job ID. Modify date, title, or caption individually or together.

Instructions

Change the publish time, title, or caption of a scheduled post by job_id.

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": {
      "job_id": "<job_id>"
    },
    "name": "edit_scheduled_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleNoNew post title/caption.
job_idYesJob ID from list_scheduled_posts or the scheduling response.
captionNoNew caption/description.
scheduled_dateNoNew ISO-8601 date/time in UTC (future, within 1 year).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior2/5

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

Description states mutation but lacks disclosure of behavioral traits like idempotency, error scenarios, or constraints beyond schema. No annotations to supplement.

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?

Single focused sentence, front-loaded, no wasted words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Minimal context for a mutation tool with 4 params and no output schema; missing success/failure info, constraints, and usage examples.

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 covers all params with descriptions; description adds minimal extra meaning beyond schema.

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 verb 'Change' and resource 'scheduled post' with identifier 'job_id', distinct from sibling cancel_scheduled_post.

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?

No guidance on when to use this tool vs alternatives, no exclusions or prerequisites.

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