Skip to main content
Glama
jginorio

Sprout Social MCP Server

by jginorio

get_users

Retrieve a list of all users in your Sprout Social account to manage team members and permissions.

Instructions

List all users in your Sprout Social account.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function for the 'get_users' tool. It calls sproutRequest with GET method to '/metadata/customer/users' and returns the result as text content.
    server.tool(
      "get_users",
      "List all users in your Sprout Social account.",
      {},
      async () => {
        const data = await sproutRequest("GET", "/metadata/customer/users");
        return { content: [{ type: "text", text: JSON.stringify(data, null, 2) }] };
      }
  • src/index.ts:130-137 (registration)
    The tool is registered via server.tool() on the McpServer instance, with the name 'get_users', a description, empty schema, and the handler callback.
    server.tool(
      "get_users",
      "List all users in your Sprout Social account.",
      {},
      async () => {
        const data = await sproutRequest("GET", "/metadata/customer/users");
        return { content: [{ type: "text", text: JSON.stringify(data, null, 2) }] };
      }
  • The sproutRequest helper function used by get_users to make authenticated API requests to the Sprout Social API.
    async function sproutRequest(
      method: "GET" | "POST",
      path: string,
      body?: Record<string, unknown>
    ): Promise<unknown> {
      const { apiKey, customerId } = getConfig();
      const url = `${SPROUT_API_BASE}/v1/${customerId}${path}`;
    
      const headers: Record<string, string> = {
        Authorization: `Bearer ${apiKey}`,
        Accept: "application/json",
      };
    
      const options: RequestInit = { method, headers };
    
      if (body) {
        headers["Content-Type"] = "application/json";
        options.body = JSON.stringify(body);
      }
    
      const response = await fetch(url, options);
    
      if (!response.ok) {
        const errorText = await response.text();
        throw new Error(
          `Sprout Social API error (${response.status}): ${errorText}`
        );
      }
    
      return response.json();
    }
  • The get_users tool has an empty schema object {}, meaning it takes no input parameters.
    {},
Behavior3/5

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

No annotations are provided, and the description only states the basic function. It does not disclose any behavioral traits such as pagination, rate limits, or what the response contains. Annotations are absent, so the description carries the burden but remains minimal.

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 concise sentence with no wasted words. It is front-loaded and communicates the purpose efficiently.

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

Completeness4/5

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

Given the tool's simplicity (0 parameters, no output schema, no annotations), the description is mostly complete. It could mention the output format, but not necessary for basic 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?

There are no parameters, and schema coverage is 100%. The description adds no parameter information, which is acceptable as no parameters exist. 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 clearly states it lists all users in the Sprout Social account, with a specific verb and resource. It distinguishes from sibling tools like get_cases or get_profiles.

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 when a list of users is needed, but provides no explicit guidance on when not to use it or alternatives. For a simple 0-parameter tool, this is adequate but not exemplary.

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/jginorio/sprout-social-mcp'

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