Skip to main content
Glama
izharikov

Sitecore Send

get_lists

Retrieve all available mailing lists from Sitecore Send to manage email campaigns and audience segmentation.

Instructions

Get all available mailing lists

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler function for the 'get_lists' tool. It fetches all mailing lists using client.lists.getAll(), maps them to a formatted string list including name, status, and ID, and returns a text content response.
    execute: async () => {
      const lists = await client.lists.getAll();
      const result = lists.MailingLists.map(x => `- '${x.Name}', status: '${x.StatusValue}', (id: '${x.ID}')`);
      return {
        content: [
          { type: "text", text: result.join("\n") }
        ]
      }
    }
  • src/tools/api.ts:12-28 (registration)
    Registration of the 'get_lists' tool on the FastMCP server, specifying name, description, annotations, and the execute handler. No input parameters defined.
    server.addTool({
      name: "get_lists",
      description: "Get all available mailing lists",
      annotations: {
        title: "Get all available mailing lists",
        openWorldHint: true,
      },
      execute: async () => {
        const lists = await client.lists.getAll();
        const result = lists.MailingLists.map(x => `- '${x.Name}', status: '${x.StatusValue}', (id: '${x.ID}')`);
        return {
          content: [
            { type: "text", text: result.join("\n") }
          ]
        }
      }
    });
Behavior3/5

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

Annotations provide openWorldHint=true, indicating this is a read operation that returns all available data. The description adds minimal behavioral context beyond this - it specifies 'all available' which reinforces completeness, but doesn't address pagination, ordering, or response format. No contradiction with annotations exists.

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?

The description is a single, efficient sentence that states exactly what the tool does with zero wasted words. It's appropriately sized for a simple retrieval tool with no parameters.

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?

For a simple read operation with no parameters and openWorldHint annotation, the description is minimally adequate. However, without an output schema, the description doesn't explain what 'mailing lists' data structure is returned, and it doesn't address how this tool differs from similar sibling tools in the context.

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

Parameters4/5

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

With 0 parameters and 100% schema description coverage, the baseline is 4. The description appropriately doesn't discuss parameters since none exist, and the schema fully documents the empty input structure.

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 verb ('Get') and resource ('all available mailing lists'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'get_single_list' or 'get_subscribers' - it's a general list retrieval tool but the scope distinction isn't explicit.

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?

The description provides no guidance on when to use this tool versus alternatives like 'get_single_list' (for specific lists) or 'get_subscribers' (for list members). There's no mention of prerequisites, limitations, or appropriate contexts for choosing this tool over siblings.

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/izharikov/send-mcp'

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