Skip to main content
Glama
jginorio

Sprout Social MCP Server

by jginorio

get_case_queues

List all case queues in your Sprout Social account to organize and manage customer support cases.

Instructions

List all case queues in your Sprout Social account.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/index.ts:160-168 (registration)
    Registration and handler for the 'get_case_queues' tool. It is registered via server.tool() with an empty schema (no parameters). The handler calls sproutRequest('GET', '/metadata/customer/queues') and returns the result as text content.
    server.tool(
      "get_case_queues",
      "List all case queues in your Sprout Social account.",
      {},
      async () => {
        const data = await sproutRequest("GET", "/metadata/customer/queues");
        return { content: [{ type: "text", text: JSON.stringify(data, null, 2) }] };
      }
    );
  • The handler function that executes the tool logic. It makes a GET request to '/metadata/customer/queues' using the sproutRequest helper, then returns the JSON response formatted as text content.
    async () => {
      const data = await sproutRequest("GET", "/metadata/customer/queues");
      return { content: [{ type: "text", text: JSON.stringify(data, null, 2) }] };
    }
  • The sproutRequest helper function used by get_case_queues to make authenticated API calls to the Sprout Social API. It prepends the customer ID to the path and adds the Bearer token header.
    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 input schema for get_case_queues is an empty object, meaning no parameters are required or accepted.
    {},
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It only states the action (list) without disclosing any behavioral traits such as whether results are paginated, ordered, or have rate limits. The read-only nature is implied but not confirmed.

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?

Single sentence, no extraneous words. Front-loaded with the action and resource. Every word earns its place.

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 no output schema and no annotations, the description provides minimal context. It does not explain what a case queue represents, the expected output format, or any side effects (none expected but unstated). For a tool with zero parameters, agents need more information to interpret the result correctly.

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?

There are no parameters, so schema coverage is 100%. The description adds context by specifying the scope ('your account'), which helps agents understand the data boundary. Baseline for zero parameters is 4, and this is met without improvement.

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 tool lists case queues and specifies the scope as 'in your Sprout Social account'. It distinguishes from sibling tools like get_cases by focusing on queues specifically, though it could be more explicit about what a case queue is.

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 versus alternatives. Sibling tools like get_cases exist but no comparison or exclusion criteria provided. Agents are left to infer usage from the name alone.

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