Skip to main content
Glama

Create list

create_list
Destructive

Create a list: a fixed group of contacts (Audience → Lists). Membership is set by hand, unlike a segment, which follows rules.

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

Input Schema

NameRequiredDescriptionDefault
nameNoList name
descriptionNoWhat the list is for

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / description / description
      Added value: +"What the list is for"
    • addedInput schema / properties / name / description
      Added value: +"List name"
  2. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false and destructiveHint=true, so the write/side-effect profile is covered structurally. The description adds domain meaning (what a list is and how membership differs from a segment), but says nothing beyond the annotations about duplicate-name handling, reversibility, or permissions. A 3 reflects real added context without behavioral disclosure.

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?

Two short sentences, zero filler, with the verb-plus-resource up front and the disambiguating contrast (hand-set vs rule-based) placed second. Every clause earns its place.

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

Completeness3/5

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

The conceptual definition and segment contrast are complete enough to pick the tool, and annotations cover the safety profile. However, with no output schema, the description never says what the call returns (e.g., the new list's ID) or what happens if a list of that name already exists, which an agent needs before calling a non-idempotent create.

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%, with both 'name' and 'description' documented inline (including maxLength 80/200), so the schema carries parameter semantics entirely. The description names no parameters and adds no format or constraint detail beyond it; baseline 3 is appropriate.

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 ('Create a list') and immediately defines the resource as 'a fixed group of contacts (Audience → Lists)', including where it lives in the product UI. It also names the concept it is most likely to be confused with (a segment), so an agent can separate create_list from create_segment 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?

The clause 'Membership is set by hand, unlike a segment, which follows rules' gives a clear rule for choosing this tool over create_segment. It does not cover the other adjacent cases, such as populating the list afterwards via add_to_list vs import_contacts, or when a segment would be preferable in practice.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.