Space Monkey Mailchimp Dashboard

Get audience geography

sm_get_member_geo

Read-onlyIdempotent

Get the country and region distribution of a project's members. Use for territory, event and travel-planning questions. Country is inferred from the member's region where possible (US states and Canadian provinces map to US and CA) before falling back to stored country data, with unresolvable values bucketed as Unknown; regions stays null unless countryCode is passed.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`projectId`	Yes	Required. The opaque alphanumeric project identifier of 8 or more characters to scope this request to. Call GET /_api/public/v1/enterprise/projects to list the project IDs available to your API key. Omitting it returns 400 VALIDATION_ERROR.
`countryCode`	No	Two-letter ISO country code to drill into, matched case-insensitively (e.g. 'US', 'CA'). Omit it and `regions` comes back null while `countries` and `allRegions` still cover the whole audience; pass it and `regions` returns that country's region breakdown.

Output Schema

TableJSON Schema

Name	Required	Description
`code`	No	A machine-readable identifier for the error type. For the full code taxonomy, see the sm_get_schema tool or the Enterprise API OpenAPI ErrorResponse component.
`error`	No	A human-readable error message detailing what went wrong.
`regions`	No	Region detail for the selected country, or null when no country was narrowed.
`countries`	No	Per-country membership rows.
`projectId`	No	An opaque alphanumeric project identifier of 8 or more characters identifying a Space Monkey Project. Treat this value as entirely opaque; do not parse, sequentialize, or auto-generate it.
`allRegions`	No	Per-region membership rows across all countries.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 11, 2026

changedInput schema / properties / countryCode / description

Previous value: -"Isolate distribution to a specific ISO country code."New value: +"Two-letter ISO country code to drill into, matched case-insensitively (e.g. 'US', 'CA'). Omit it and `regions` comes back null while `countries` and `allRegions` still cover the whole audience; pass it and `regions` returns that country's region breakdown."

Changed14 schema fields changedSep 11, 2026
- changedOutput schema / description
```
Previous value: -"Output for the sm_get_member_geo tool. Failure payloads arrive in the same envelope as { error, message, code }."New value: +"Output for the sm_get_member_geo tool. Failure payloads arrive in the same envelope as { error, code }."
```
- addedOutput schema / properties / allRegions / description
```
Added value: +"Per-region membership rows across all countries."
```
- addedOutput schema / properties / allRegions / items / properties / countryCode / description
```
Added value: +"Two-letter country code."
```
- addedOutput schema / properties / allRegions / items / properties / region / description
```
Added value: +"Region name within the country."
```
- addedOutput schema / properties / allRegions / items / properties / subscribed / description
```
Added value: +"Subscribed members in the region."
```
- addedOutput schema / properties / allRegions / items / properties / total / description
```
Added value: +"Total members in the region."
```
- addedOutput schema / properties / countries / description
```
Added value: +"Per-country membership rows."
```
- addedOutput schema / properties / countries / items / properties / countryCode / description
```
Added value: +"Two-letter country code."
```
- addedOutput schema / properties / countries / items / properties / subscribed / description
```
Added value: +"Subscribed members in the country."
```
- addedOutput schema / properties / countries / items / properties / total / description
```
Added value: +"Total members in the country."
```
- addedOutput schema / properties / regions / description
```
Added value: +"Region detail for the selected country, or null when no country was narrowed."
```
- addedOutput schema / properties / regions / items / properties / region / description
```
Added value: +"Region or state-level location string, or null when unknown."
```
- addedOutput schema / properties / regions / items / properties / subscribed / description
```
Added value: +"Subscribed members in the region."
```
- addedOutput schema / properties / regions / items / properties / total / description
```
Added value: +"Total members in the region."
```

Changed3 schema fields changedSep 10, 2026

addedInput schema / properties / countryCode / description

Added value: +"Isolate distribution to a specific ISO country code."

addedInput schema / properties / projectId / description

Added value: +"Required. The opaque alphanumeric project identifier of 8 or more characters to scope this request to. Call GET /_api/public/v1/enterprise/projects to list the project IDs available to your API key. Omitting it returns 400 VALIDATION_ERROR."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "description": "Output for the sm_get_member_geo tool. Failure payloads arrive in the same envelope as { error, message, code }.",
+  "properties": {
+    "allRegions": {
+      "items": {
+        "additionalProperties": true,
+        "description": "Granular region-to-country groupings.",
+        "properties": {
+          "countryCode": {
+            "type": "string"
+          },
+          "region": {
+            "type": "string"
+          },
+          "subscribed": {
+            "type": "integer"
+          },
+          "total": {
+            "type": "integer"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "code": {
+      "description": "A machine-readable identifier for the error type. For the full code taxonomy, see the sm_get_schema tool or the Enterprise API OpenAPI ErrorResponse component.",
+      "type": "string"
+    },
+    "countries": {
+      "items": {
+        "additionalProperties": true,
+        "description": "Member counts grouped by country code.",
+        "properties": {
+          "countryCode": {
+            "type": "string"
+          },
+          "subscribed": {
+            "type": "integer"
+          },
+          "total": {
+            "type": "integer"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "error": {
+      "description": "A human-readable error message detailing what went wrong.",
+      "type": "string"
+    },
+    "projectId": {
+      "description": "An opaque alphanumeric project identifier of 8 or more characters identifying a Space Monkey Project. Treat this value as entirely opaque; do not parse, sequentialize, or auto-generate it.",
+      "type": "string"
+    },
+    "regions": {
+      "items": {
+        "additionalProperties": true,
+        "description": "Member counts grouped by broader regional assignment.",
+        "properties": {
+          "region": {
+            "type": "string"
+          },
+          "subscribed": {
+            "type": "integer"
+          },
+          "total": {
+            "type": "integer"
+          }
+        },
+        "type": "object"
+      },
+      "type": [
+        "array",
+        "null"
+      ]
+    }
+  },
+  "type": "object"
+}

First observedSep 10, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Annotations already declare read-only, idempotent and open-world, so safety is covered. Beyond that the description discloses meaningful derivation behavior: country is inferred from region (US states/CA provinces mapped), falls back to stored country data, and unresolvable values are bucketed as Unknown, plus the non-obvious rule that regions is null unless countryCode is passed.

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?

Three dense sentences, front-loaded with the purpose and followed by usage context and the derivation caveat. Slight redundancy with the schema on the countryCode/regions behavior keeps it from a 5.

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?

An output schema exists, so return-shape explanation is unnecessary. The description supplies the usage context and the data-derivation edge cases (region inference, Unknown bucket, conditional regions) that an agent needs to interpret results correctly.

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% and both parameters are thoroughly documented there, including the countryCode case-insensitivity and the regions-null behavior. The description largely restates that schema contract rather than adding new syntax or format guidance, so the baseline 3 applies.

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: 'Get the country and region distribution of a project's members.' This is precise enough to separate it from sibling member-metrics tools such as sm_get_member_overview or sm_get_member_growth without opening either schema.

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

Usage Guidelines4/5

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

'Use for territory, event and travel-planning questions' gives a concrete use context and implies the questions this tool answers. It stops short of naming when-not-to-use or an explicit alternative sibling, so it is not a full 5.

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

All Space Monkey Mailchimp Dashboard 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.

Resources

Need Help?