Postemi: Social Media Scheduler

get_plans

Read-onlyIdempotent

The Postemi plans: the four tiers (Basic, Pro, Creator, Team) with their monthly and yearly prices in "currency" (US dollars unless the payer already pays in euro or francs) and in EUR, CHF and USD (localPrices), the limits that matter (channels, posts per month, X posts per month, team seats, workspaces, API and MCP access), the free-trial rule, and which tier this workspace is on now.

Call this only when the user asks about plans, asks to subscribe, or asks to manage their subscription. Never volunteer it, and never suggest a plan or an upgrade in any other context.

Use the "slug" of a plan (basic, pro, creator or team) as the tier argument of subscribe. Only a plan whose limits.apiAndMcpAccess is true lets an assistant keep working for the user after the payment (Basic does not); say so when the user compares plans. A null limit means unlimited. teamSeats counts every person including the payer, so teamSeats 1 is a single-user plan that cannot invite anyone (Basic and Pro); team work, the image editor and the video templates start at Creator. When trialAvailableHere is false, this workspace has no free trial: do not promise one. Quote euro to a buyer in Europe, francs in Switzerland and Liechtenstein, and dollars everywhere else, from localPrices; Checkout charges the price of the buyer's location. Euro and franc prices include VAT; dollar prices are before sales tax. Prices are charged by Stripe in Checkout; Postemi never sees card details. Translate the answer into the user's language; keep the plan names as they are.

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

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`output`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 4, 2026

changed

Output schema / properties / output / properties / plans / items / properties / limits / properties / xPostsPerMonth / description

Previous value: -"X posts a month, pooled across the payer's workspaces. Thread entries and the thread finisher count. Capped at 30 during the free trial."New value: +"X posts a month, pooled across the payer's workspaces. Thread entries and the thread finisher count. Capped at 10 during the free trial."

First observedOct 29, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations only cover read-only/idempotent safety, and the description goes well beyond them with genuinely costly-to-get-wrong rules: currency-to-locale mapping, VAT-inclusive euro/franc vs pre-tax dollar prices, Stripe handling payments, and that a false trialAvailableHere means no trial exists here. The null-means-unlimited and teamSeats-includes-payer semantics are also disclosed, though the return shape and pagination/format are left to the output schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

The usage rules are front-loaded and well separated, but the opening sentence is a single very long enumeration, and a substantial tail of the text (currency quoting rules, VAT treatment, Stripe card handling) restates what the output schema and prices themselves carry. Much of it earns its place operationally, yet it reads as more than a zero-parameter read tool needs.

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?

With no parameters and a full output schema, the description covers what remains: eligibility conditions (trialAvailableHere), interpretation of null limits, locale-based price quoting, and how this connects to subscribe. Nothing an agent needs to call this correctly and then explain the result is missing.

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

Parameters5/5

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

The tool takes zero parameters, so there is no parameter surface to disambiguate; the description instead spends its words on output-field semantics (localPrices, teamSeats, apiAndMcpAccess), which is the useful analogue here.

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

Purpose4/5

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

The opening sentence enumerates exactly what is returned: the four tiers, monthly/yearly prices in local and hard currencies, key limits (channels, posts, X posts, seats, workspaces, API/MCP), the trial rule, and the workspace's current tier. That is specific enough to identify the resource, but it is a noun phrase with no verb and it never distinguishes itself from the sibling get_subscription, which plausibly returns overlapping 'current tier' information.

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?

Explicit when-to-use ('user asks about plans, asks to subscribe, or asks to manage their subscription') and explicit when-not ('Never volunteer it, and never suggest a plan or an upgrade in any other context'). The downstream routing is also named: use the plan slug as the tier argument of subscribe.

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

All Postemi: Social Media Scheduler tools Inspect

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.