Skip to main content
Glama
Sign In

PostPen

by ai.postpen
OverviewDiscussionsAdmin

List social prompts

list_prompts
Read-only

Lists PostPen Social Prompts: the user's own prompts first, then the public library, most used first. A prompt is instructions for writing a post: follow them with the user's own topic and voice, and check the result against each network's limits before save_draft. Each prompt has id, title, description, tags (filter values such as hooks or listicle), own (true for the user's own), public, uses, inspired_by (links of Inspiration Hub posts it was made from) and a short preview. get_prompt returns one prompt's full instructions. When the user names a prompt ("use my founder story prompt"), find it here.

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

Input Schema

NameRequiredDescriptionDefault
tagNoOnly prompts with this tag, e.g. hooks, listicle, hook-story.
mineNotrue lists only the user's own prompts.
limitNoHow many prompts to return. Defaults to 20; values above 50 return 50.
queryNoWords that must all appear in the title, description, instructions or tags.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already cover read-only, non-destructive, closed-world, so the description's added value is ordering rules and the returned field list (id, title, tags, own, public, uses, inspired_by, preview), which is genuinely useful. It does not cover edge behavior such as empty results or how many results the default returns, so it falls short of a full 5.

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?

Ordering behavior is front-loaded in the first sentence, and the field enumeration is compact. The mid-sentence workflow aside about applying prompts to the user's topic and checking network limits is slightly tangential to a listing tool, but still earns its place as context.

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

Completeness5/5

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

No output schema exists, and the description compensates by enumerating every returned field and the sort order, which is exactly what an agent needs to interpret results. Combined with the get_prompt handoff, nothing essential to correct invocation is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds meaning by tieing the tag filter to the returned `tags` field and giving example values (hooks, listicle). It does not elaborate on `mine`, `limit`, or `query` beyond what the schema already states.

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 (list PostPen Social Prompts) plus ordering semantics: own prompts first, then public library, most used first. It also defines what a prompt is and distinguishes it from get_prompt, so it is clearly separable from the sibling tools.

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?

Explicitly routes between this tool and get_prompt ("get_prompt returns one prompt's full instructions") and gives a concrete trigger scenario ("use my founder story prompt" → find it here). It also notes downstream workflow: check the output against network limits before save_draft.

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

All PostPen toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources