Skip to main content
Glama

Update Contact List

neuron_update_contact_list

Update a contact list's name, slug, description, criteria, or refresh schedule to maintain accurate and relevant audience segments.

Instructions

Update a contact list's name, slug, description, criteria, or refresh schedule

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoNew name
slugNoNew slug
criteriaNoFor dynamic lists: criteria rules/AI prompt. Set to null to clear.
idOrSlugYesThe list ID (UUID) or slug
descriptionNoNew description
refreshScheduleNoRefresh schedule for dynamic lists
Behavior1/5

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

No annotations are provided, and the description does not disclose any behavioral traits such as permissions required, side effects, or whether the operation is destructive.

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?

The description is one sentence listing the updatable fields, which is concise but could be more effective with a usage note.

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 output schema, and no annotations, the description is insufficient; it lacks explanation of response and constraints on fields.

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 coverage is 100% with descriptions for each parameter, so the description adds little beyond listing the fields; 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?

The description states a specific verb ('Update') and resource ('contact list') and lists the fields that can be updated, distinguishing it from sibling CRUD tools.

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 vs alternatives, no prerequisites, and no exclusions provided.

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/conquext/neuron-mcp-server'

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