Skip to main content
Glama
Sign In
@posteahora/mcp

@posteahora/mcp

Official
by posteahora
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Create a post idea

create_idea

Save brainstorming ideas to a backlog without publishing. Keep them for later promotion to social posts.

Instructions

Add a lightweight idea to the backlog. Use this for brainstorming — it does NOT publish anything. Promote to a real post later with create_post.

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

Input Schema

NameRequiredDescriptionDefault
tagsNoFreeform tags
titleNoShort title for the idea
statusNoKanban column; defaults to unassigned
captionNoDraft caption / body text
mediaUrlsNoPublic media URLs (from upload_media)

Output Schema

NameRequiredDescriptionDefault
ideaYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations only provide false hints for readOnly, idempotent, and destructive, which convey little. The description adds meaningful behavior: it is a lightweight insertion into a backlog and does NOT publish anything, which goes beyond the structured data.

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?

Two tight sentences, front-loaded with the action and resource, and every word contributes value. No redundancy or filler.

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

Completeness4/5

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

For a simple creation tool with output schema and fully described parameters, the description covers the core purpose, usage context, and relationship to the key sibling tool (create_post). It doesn't mention update_idea or delete_idea, but that is not essential for basic use.

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 input schema covers all five parameters with individual descriptions (100% coverage), so the description does not need to add parameter details. The schema already provides semantic meaning for each property.

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?

The description clearly states 'Add a lightweight idea to the backlog' with a specific verb and resource, and explicitly distinguishes from create_post by noting it does not publish anything and is later promoted via create_post.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explicitly says 'Use this for brainstorming' and contrasts with the alternative create_post, explaining that this tool does not publish and that promotion happens later. This gives clear when-to-use and when-not-to-use guidance.

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