Skip to main content
Glama
Sign In
Marketic

Marketic

by Das-rebel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

hub_create_segment

Create audience segments across all connected marketing platforms using custom conditions and descriptions for targeted campaigns.

Instructions

Create an audience segment across ALL connected marketing platforms.

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

Input Schema

NameRequiredDescriptionDefault
nameYes
conditionsNo
descriptionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

C2.4/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden. It conveys the mutation ('Create') and the cross-platform scope ('across ALL connected marketing platforms'), but it does not disclose side effects, reversibility, permission requirements, or what happens to existing segments. The cross-platform behavior is the only behavioral hint.

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

Conciseness3/5

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

The description is a single concise sentence with no fluff, but it is under-specified. It front-loads the action but omits necessary context, so it is not appropriately sized for the tool's complexity.

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?

Given three parameters, no output schema, and no annotations, the description is minimal and incomplete. It does not explain the purpose of each parameter, expected behavior, or any constraints, leaving much to inference.

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?

Schema coverage is 0%, and the description provides no detail about the parameters (name, conditions, description). It only reiterates the purpose without explaining what conditions or description mean, leaving the agent without guidance on how to construct a valid segment.

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 action (Create), the resource (audience segment), and the scope (across ALL connected marketing platforms). This distinguishes it from CRM create tools and general broadcast tools, though it doesn't explicitly name a sibling or contrast with one.

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 is provided on when to use this tool versus alternatives, such as when to choose hub_create_segment over hub_sync_contact or building a segment through another tool. There is no explicit context, prerequisites, or exclusion criteria.

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