Skip to main content
Glama
Mohit4022-cloud

Marketing Automation MCP Server

analyze_audience_segments

Analyze audience segments by criteria like demographics or behavior to generate structured insights for targeted marketing.

Instructions

Analyze audience segments in deterministic demo mode or return a structured live-mode block.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
contact_list_idYes
criteriaYes
min_segment_sizeNo
max_segmentsNo
include_recommendationsNo
analyze_overlapNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
statusNook
modeNolive
blocked_reasonNo
warningsNo
analysis_idYes
total_contactsYes
segmentsYes
uncategorized_countYes
overlapsNo
recommendationsYes
insightsYes
created_atYes
Behavior2/5

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

No annotations are provided, and the description fails to disclose behavioral traits such as read/write nature, side effects, or mode implications. 'Deterministic demo mode' hints at reproducibility but is not explained.

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

Conciseness2/5

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

The description is a single sentence, but it is under-specified rather than concise. It omits critical details that would justify its brevity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 6 parameters, no annotations, and no explanation of the output schema, the description is insufficient for an agent to correctly invoke the tool. The live-mode vs. demo distinction is mentioned but not fleshed out.

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

Parameters1/5

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

The input schema has 0% description coverage for its 6 parameters, and the description does not mention or clarify any parameters. It adds no value beyond the schema's field names.

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 description clearly states the tool analyzes audience segments and mentions two modes (deterministic demo vs. live), which distinguishes it from sibling tools like create_campaign_copy or generate_campaign_report. However, it lacks specificity on what the analysis produces.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives; no prerequisites or context for the modes. The description only states the action without any conditional advice.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Mohit4022-cloud/Marketing-Automation-MCP-Server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server