Skip to main content
Glama
izharikov

Sitecore Send

get_subscribers

Retrieve subscriber data from a Sitecore Send mailing list to manage contacts and analyze audience engagement.

Instructions

Get subscribers of a mailing list

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
listIdYesId of the mailing list

Implementation Reference

  • Handler function that retrieves subscribers from a specified mailing list using SendClient, maps them to a formatted string list, and returns as text content.
    execute: async ({ listId }) => {
      const response = await client.subscribers.fromList(listId);
      const result = response.Subscribers.map(x => `- '${x.Email}', Name: '${x.Name}', Tags: [${x.Tags.join(", ")}]`);
      return {
        content: [
          { type: "text", text: result.join("\n") }
        ]
      }
    },
  • Zod schema defining the input parameter: listId as a UUID string.
    parameters: z.object({
      listId: z.string().uuid().describe("Id of the mailing list")
    }),
  • src/tools/api.ts:53-72 (registration)
    Registration of the 'get_subscribers' tool using server.addTool, including name, description, schema, annotations, and handler.
    server.addTool({
      name: "get_subscribers",
      description: "Get subscribers of a mailing list",
      parameters: z.object({
        listId: z.string().uuid().describe("Id of the mailing list")
      }),
      annotations: {
        title: "Get subscribers of a mailing list",
        openWorldHint: true,
      },
      execute: async ({ listId }) => {
        const response = await client.subscribers.fromList(listId);
        const result = response.Subscribers.map(x => `- '${x.Email}', Name: '${x.Name}', Tags: [${x.Tags.join(", ")}]`);
        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 tool may return partial data, but the description doesn't add behavioral context beyond this. It doesn't explain what 'subscribers' includes (e.g., email addresses, names, status) or mention pagination, rate limits, or error handling. With annotations covering some aspects, the description adds minimal value, scoring a baseline 3.

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, direct sentence with no wasted words, making it highly concise and front-loaded. It efficiently communicates the core purpose without unnecessary elaboration, earning a top score for brevity and clarity.

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 low complexity (one parameter, no output schema) and annotations providing openWorldHint, the description is minimally adequate. However, it lacks details on return format (e.g., list structure, fields) and doesn't compensate for the absence of an output schema, leaving gaps in completeness for agent usage.

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 the 'listId' parameter fully documented as a UUID. The description doesn't add any parameter details beyond what the schema provides, such as example values or constraints, so it meets the baseline of 3 for high schema coverage without extra semantic value.

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 ('Get') and resource ('subscribers of a mailing list'), making the purpose immediately understandable. However, it doesn't explicitly distinguish this tool from sibling tools like 'get_subscriber_by_email' or 'get_lists', which would require more specific differentiation to earn a 5.

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. It doesn't mention sibling tools like 'get_subscriber_by_email' for individual lookups or 'get_lists' for listing mailing lists, leaving the agent to infer usage context without explicit direction.

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