Skip to main content
Glama

List recurring and evergreen campaigns

list_post_campaigns
Read-onlyIdempotent

List a profile's recurring (repeat one post) and evergreen (rotating library) post campaigns with schedule, status, counts and next date. Only the next post of each campaign is ever a real scheduled post.

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": {
      "profile_id": "<profile_id>"
    },
    "name": "list_post_campaigns"
  }
}

Input Schema

NameRequiredDescriptionDefault
statusNo
profile_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, closed-world), so the bar is lower. The description still adds genuinely non-obvious behavior: that only the next post of each campaign exists as a real scheduled post, which prevents an agent from expecting a full materialized schedule. It does not say how statuses affect results or what pagination/limits exist.

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?

Two sentences, front-loaded with the resource and scope, with the caveat second. No filler, though the returned-field list ('schedule, status, counts and next date') could be trimmed or repurposed to explain the filter.

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?

With no output schema, listing the returned fields is useful, and the 'only the next post is real' note fills a real comprehension gap. However, the unexplained status filter and the absence of any guidance relative to get_post_campaign leave an agent guessing on invocation specifics for a two-parameter tool.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must carry parameter meaning. It never explains the required profile_id or that the optional 'status' parameter is a filter restricted to active/paused/completed/cancelled — mentioning 'status' only as a returned field actively risks the agent treating it as output-only.

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?

States a specific verb and resource ('List a profile's recurring ... and evergreen ... post campaigns') and explains both campaign types inline ('repeat one post', 'rotating library'). It does not distinguish itself from the sibling get_post_campaign (singular), so an agent must infer the list-vs-single distinction.

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

Usage Guidelines3/5

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

The use case is implied by 'List a profile's ... campaigns', but there is no explicit statement of when to choose this over get_post_campaign, list_posts, or preview_campaign_dates. No prerequisites, no exclusions, no alternative routing.

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.

Resources