Skip to main content
Glama
Sign In
Mailchimp MCP

Mailchimp MCP

by damientilman
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

get_promo_rule

Read-only

Retrieve a single promo rule by ID to inspect its full configuration before updating or to confirm existence before attaching new codes.

Instructions

Retrieve a single promo rule by ID with its full configuration.

Use to inspect a rule's current settings before updating, or to confirm a rule exists before attaching new codes. Use list_promo_rules to browse and discover IDs.

Returns 404 if store_id or promo_rule_id is invalid.

Args: store_id: E-commerce store ID. promo_rule_id: Rule ID to inspect.

Returns: JSON with id, title, description, amount, type, target, enabled, starts_at, ends_at, created_at, updated_at.

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": {
      "store_id": "<store_id>",
      "promo_rule_id": "<promo_rule_id>"
    },
    "name": "get_promo_rule"
  }
}

Input Schema

NameRequiredDescriptionDefault
accountNo
store_idYes
promo_rule_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.7.1
    • addedInput schema / properties / account
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Account"
+}
  2. Addedv0.5.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true. Description adds that it returns 404 for invalid store_id or promo_rule_id, and lists returned fields, which provides context beyond annotations. Rate limits or auth are not mentioned but are acceptable for a simple read operation.

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?

Description is well-structured: purpose sentence, usage guidance, error behavior, args list, return list. No wasted words, each sentence adds value.

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?

Given the tool's simplicity, the description covers all essential aspects: purpose, when to use, alternatives, error conditions, parameters, and return values. No gaps given that an output schema exists and annotations are present.

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 0%, so description must explain parameters. It explains store_id and promo_rule_id briefly but omits the optional account parameter entirely. The returned fields list helps but doesn't cover all params.

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 the tool retrieves a single promo rule by ID with full configuration, using a specific verb and resource. It distinguishes from siblings like list_promo_rules for browsing IDs.

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 says when to use: inspect before updating or confirm existence before attaching codes. Provides alternative: use list_promo_rules to discover IDs. Also notes 404 for invalid IDs.

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