Skip to main content
Glama
jginorio

Sprout Social MCP Server

by jginorio

get_teams

Retrieve a list of all teams configured in your Sprout Social account.

Instructions

List all teams in your Sprout Social account.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The 'get_teams' tool handler. It is registered via server.tool(), accepts no parameters (empty schema {}), makes a GET request to /metadata/customer/teams, and returns the JSON response as text content. This is both the handler and registration.
    server.tool(
      "get_teams",
      "List all teams in your Sprout Social account.",
      {},
      async () => {
        const data = await sproutRequest("GET", "/metadata/customer/teams");
        return { content: [{ type: "text", text: JSON.stringify(data, null, 2) }] };
      }
  • The input schema for get_teams is an empty object ({}) — no parameters are required.
    {},
  • src/index.ts:150-158 (registration)
    The tool is registered using server.tool() on the McpServer instance. Registration, handler, and schema are all in the same call.
    server.tool(
      "get_teams",
      "List all teams in your Sprout Social account.",
      {},
      async () => {
        const data = await sproutRequest("GET", "/metadata/customer/teams");
        return { content: [{ type: "text", text: JSON.stringify(data, null, 2) }] };
      }
    );
  • The sproutRequest helper function used by get_teams to make the actual API GET request to the Sprout Social API. It constructs the URL with customer ID, sets auth headers, and parses the JSON response.
    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();
    }
Behavior3/5

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

No annotations provided, so the description carries full burden. It implies a read-only operation but does not mention any additional behavioral traits like pagination, rate limits, or data format.

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, front-loaded with action and resource, no wasted words.

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

Completeness5/5

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

For a parameterless, read-only list tool with no output schema, the description fully suffices. No missing details.

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?

No parameters exist in the input schema (coverage 100%). With 0 parameters, baseline is 4; the description adds no parameter info, which is acceptable.

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 the action ('List') and the resource ('all teams') with scope ('in your Sprout Social account'), distinguishing it from siblings like get_cases or get_groups.

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?

No guidance on when to use this tool versus alternatives. While the purpose is clear, the description lacks explicit context for selection among many list tools.

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