Skip to main content
Glama
jginorio

Sprout Social MCP Server

by jginorio

get_profiles

List all social profiles connected to your Sprout Social account to view and manage linked networks.

Instructions

List all social profiles connected to your Sprout Social account.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler for the 'get_profiles' tool. Calls sproutRequest with GET /metadata/customer to list all social profiles connected to the Sprout Social account.
    server.tool(
      "get_profiles",
      "List all social profiles connected to your Sprout Social account.",
      {},
      async () => {
        const data = await sproutRequest("GET", "/metadata/customer");
        return { content: [{ type: "text", text: JSON.stringify(data, null, 2) }] };
      }
    );
  • src/index.ts:100-108 (registration)
    Registration of the 'get_profiles' tool on the McpServer instance. No input schema needed (empty object).
    server.tool(
      "get_profiles",
      "List all social profiles connected to your Sprout Social account.",
      {},
      async () => {
        const data = await sproutRequest("GET", "/metadata/customer");
        return { content: [{ type: "text", text: JSON.stringify(data, null, 2) }] };
      }
    );
  • Helper function sproutRequest used by the get_profiles handler. Makes authenticated GET/POST 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();
    }
Behavior4/5

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

No annotations exist, so the description carries full burden. It clearly indicates a read-only operation (listing) with no destructive side effects. It does not mention authentication or rate limits, but for a simple list this is adequate.

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?

A single, front-loaded sentence with zero waste. Every word is necessary and clear.

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 zero-parameter tool without output schema, the description fully captures the tool's purpose and behavior. No additional details are needed.

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

Parameters5/5

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

The input schema has no parameters (coverage 100%), so the description adds no extra param info, which is appropriate. The description is sufficient for a parameterless tool.

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 explicitly states the verb 'List' and the resource 'social profiles', clearly distinguishing it from sibling tools like get_messages or get_cases.

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 for retrieving connected profiles but provides no explicit when-to-use, when-not-to-use, or alternative tools. Given the simplicity of a zero-parameter list, minimal guidance is acceptable.

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