Skip to main content
Glama

Save this week's posts

social_posts_save

Saves the week's posts once the founder has seen them (routines/posts.md step 5): each with its slot number, format, audience, hook, caption, local time, and the asset ids from assets_save when the files are in Assets. A post saved again with the same n replaces it. Every platform starts as planned. Free.

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": {
      "tz": "<tz>",
      "posts": "<posts>"
    },
    "name": "social_posts_save"
  }
}

Input Schema

NameRequiredDescriptionDefault
tzYes
postsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior3/5

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

Beyond the annotations (readOnlyHint false, destructiveHint false, openWorldHint false), it discloses genuinely useful behavior: same-n saves replace the prior post, every platform starts as planned, and the call is free. It does not say what is lost when a post is replaced or what happens on validation failure, and the annotations already establish the write-safe, non-destructive-external profile.

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?

Dense and front-loaded, one paragraph with no filler; the replacement rule and default platform status each earn their clause. Some phrasing is telegraphic ("Free."), but nothing is wasted.

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?

Given a nested 8-field post object, a required tz parameter, and no output schema, the description covers the core fields but omits how tz interacts with the local-time `at` value and what the call returns. Adequate to attempt a call, not complete enough to call confidently.

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?

The description maps most nested post fields to plain meaning (slot number, format, audience, hook, caption, local time, asset ids), compensating for the near-zero schema description coverage. However, the required top-level tz parameter, remakeOf, and the platform values are undocumented in either place, leaving a real gap.

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?

States a specific verb and resource ("Saves the week's posts") plus the gating condition ("once the founder has seen them"), and pins it to a workflow step in routines/posts.md step 5. It also distinguishes the write shape from a plain update by explaining that re-saving with the same n replaces the post.

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?

Gives a clear when-to-use trigger (after founder review, step 5 of the routine) and names the upstream dependency on assets_save for asset ids. It stops short of stating when to use social_posts_update instead of re-saving here, so the boundary with that sibling is left implicit.

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.