Skip to main content
Glama

createGroup

Create a new group or list in the Clay MCP server, ensuring no duplicates unless specified. Manage contacts, notes, and reminders efficiently with organized groupings.

Instructions

Create a group or list for the user. If a group with the same name already exists, it will not create a duplicate unless explicitly requested to ignore the check.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYesThe name of the group to create.

Implementation Reference

  • index.js:265-273 (registration)
    Registration of the MCP tool 'createGroup' using server.addTool, including name, description, input parameters schema, and execute handler.
    server.addTool({
      name: "createGroup",
      description:
        "Create a group or list for the user. If a group with the same name already exists, it will not create a duplicate unless explicitly requested to ignore the check.",
      parameters: z.object({
        title: z.string().describe("The name of the group to create."),
      }),
      execute: async (params) => callTool("/create-group", params),
    });
  • Input schema for the createGroup tool, requiring a 'title' string parameter.
    parameters: z.object({
      title: z.string().describe("The name of the group to create."),
    }),
  • Handler function for createGroup tool that proxies the request to the external /create-group endpoint via the shared callTool function.
    execute: async (params) => callTool("/create-group", params),
  • Shared helper function callTool that handles HTTP requests to the external Clay API endpoints for all proxied tools, including createGroup.
    async function callTool(path, params, session) {
      console.log('Calling tool', path, session)
      return fetch(`https://nexum.clay.earth/tools${path}`, {
        body: JSON.stringify(params),
        headers: {
          Authorization: `ApiKey ${session.apiKey}`,
          "Content-Type": "application/json",
        },
        method: "POST",
      }).then((res) => res.text());
    }
Behavior3/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 discloses a key behavioral trait: the duplicate-check logic and optional override. However, it lacks details on permissions, rate limits, error handling, or what the response looks like (since no output schema exists).

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 two sentences with zero waste—each sentence adds value (purpose and behavioral nuance). It's appropriately sized and front-loaded with the core purpose, though it could be slightly more structured (e.g., bullet points for behaviors).

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?

Given the tool's complexity (a write operation with behavioral nuance), no annotations, and no output schema, the description is moderately complete. It covers the core purpose and a key behavior but misses details like response format, error cases, or authentication requirements, leaving gaps for an agent.

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%, so the schema already documents the 'title' parameter. The description adds no additional parameter semantics beyond what's in the schema (e.g., format constraints, examples). The baseline of 3 is appropriate when the schema does the heavy lifting.

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 a group or list') and the resource ('for the user'), making the purpose unambiguous. It doesn't explicitly distinguish from siblings like 'updateGroup' or 'getGroups', but the verb 'create' inherently differentiates it from read/update operations.

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

Usage Guidelines3/5

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

The description implies usage context through the duplicate-check behavior ('If a group with the same name already exists...'), suggesting it's for creating new groups. However, it doesn't explicitly state when to use this versus alternatives like 'updateGroup' or provide prerequisites (e.g., authentication needs).

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

Related 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/clay-inc/clay-mcp'

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