Skip to main content
Glama
jginorio

Sprout Social MCP Server

by jginorio

get_client

Retrieve customer IDs and names from your Sprout Social account.

Instructions

Get your Sprout Social customer IDs and names.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/index.ts:90-98 (registration)
    The tool 'get_client' is registered using server.tool() with no input schema (empty object {}) and a handler that calls sproutMetadataRequest('/metadata/client').
    server.tool(
      "get_client",
      "Get your Sprout Social customer IDs and names.",
      {},
      async () => {
        const data = await sproutMetadataRequest("/metadata/client");
        return { content: [{ type: "text", text: JSON.stringify(data, null, 2) }] };
      }
    );
  • The handler for 'get_client' - an async function that fetches metadata via sproutMetadataRequest('/metadata/client') and returns the result as JSON text content.
    async () => {
      const data = await sproutMetadataRequest("/metadata/client");
      return { content: [{ type: "text", text: JSON.stringify(data, null, 2) }] };
    }
  • The schema/input for 'get_client' is an empty object {}, meaning it takes no parameters.
    {},
  • Helper function sproutMetadataRequest() used by the get_client handler to make the GET request to '/metadata/client'.
    async function sproutMetadataRequest(path: string): Promise<unknown> {
      const { apiKey } = getConfig();
      const url = `${SPROUT_API_BASE}/v1${path}`;
    
      const response = await fetch(url, {
        method: "GET",
        headers: {
          Authorization: `Bearer ${apiKey}`,
          Accept: "application/json",
        },
      });
    
      if (!response.ok) {
        const errorText = await response.text();
        throw new Error(
          `Sprout Social API error (${response.status}): ${errorText}`
        );
      }
    
      return response.json();
    }
Behavior2/5

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

No annotations provided; description lacks behavioral details like response format, pagination, or authentication requirements. Minimal disclosure beyond name.

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 redundancy, front-loaded with key verb 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?

For a parameterless tool, description is too sparse. Lacks scope (e.g., all customers? authenticated user's?), output format, or relation to siblings.

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?

No parameters exist, so schema coverage is 100%. Description adds minimal context ('IDs and names') but does not go beyond the tool's implied output.

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?

Description clearly states verb 'Get' and specific resource 'your Sprout Social customer IDs and names', distinguishing from sibling tools like get_users and 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 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. Siblings cover users, profiles, etc., but no contextual cues provided.

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