Skip to main content
Glama
pushengage-mcp

pushengage-mcp

List RSS auto push campaigns

pushengage_list_rss_campaigns
Read-only

Lists RSS auto push campaigns for a site with pagination and optional status filtering to review or manage feeds.

Instructions

Lists the RSS auto push campaigns on the current site, paginated (response includes has_more). Each item includes the feed_url. Optionally filter by status (default "all" = every status), mirroring the dashboard filter tabs.

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

Input Schema

NameRequiredDescriptionDefault
pageNoPage number (1-indexed).
limitNoHow many to return per page. Min 1, max 100, default 10.
statusNoFilter by status. "all" (default) returns every status.all
site_idNoOverride the currently selected site.

Output Schema

NameRequiredDescriptionDefault
pageNo
limitNo
totalNo
has_moreNo
campaignsNo
last_pageNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv1.2.0
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / page / maximum
      Added value: +9007199254740991
    • addedInput schema / properties / site_id / maximum
      Added value: +9007199254740991
    • changedOutput schema / additionalProperties
      Previous value: -trueNew value: +{}
    • changedOutput schema / properties / campaigns / items / additionalProperties
      Previous value: -trueNew value: +{}
  2. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds that results are paginated via `has_more` and that each item carries `feed_url`, plus the default-status behavior — useful but partly redundant given an output schema exists. No auth, rate-limit, or site-selection behavior is disclosed beyond the schema's site_id wording.

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 tight sentences with the resource and scope front-loaded and zero filler. Minor redundancy with schema-documented defaults and return fields keeps it from being maximally efficient.

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 read-only paginated list tool with a full output schema and 100%-documented parameters, the description covers purpose, scope, pagination, and item contents adequately. It leaves only the site-override semantics to the schema, which is reasonable.

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?

Schema description coverage is 100%, so page, limit, status, and site_id are already documented; baseline is 3. The description echoes the status default semantics ("default all = every status") but adds nothing new about pagination params or how site_id overrides the selected site.

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 ("Lists the RSS auto push campaigns") plus scope ("on the current site"), which distinguishes it from the drip/triggered campaign listers by resource type. It stops short of explicitly naming a sibling to route away from, so it is clear but not fully differentiated.

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?

Usage is implied: use it to enumerate RSS auto push campaigns, optionally filtered by status. There is no explicit when-to-use vs. when-to-use-another-tool guidance, and no prerequisites or exclusions are stated.

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