Skip to main content
Glama
jginorio

Sprout Social MCP Server

by jginorio

get_topics

List all listening topics in your Sprout Social account to view and manage monitored conversations.

Instructions

List all listening topics in your Sprout Social account.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/index.ts:140-148 (registration)
    Registration of the 'get_topics' tool via server.tool(). No separate schema (empty object) and handler is inline.
    server.tool(
      "get_topics",
      "List all listening topics in your Sprout Social account.",
      {},
      async () => {
        const data = await sproutRequest("GET", "/metadata/customer/topics");
        return { content: [{ type: "text", text: JSON.stringify(data, null, 2) }] };
      }
    );
  • Handler function for get_topics: calls sproutRequest with GET /metadata/customer/topics and returns the JSON data.
    async () => {
      const data = await sproutRequest("GET", "/metadata/customer/topics");
      return { content: [{ type: "text", text: JSON.stringify(data, null, 2) }] };
    }
  • Schema for get_topics is an empty object (no input parameters required).
    {},
Behavior4/5

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

The description clearly indicates a read-only listing operation with no destructive side effects. Although no annotations are present, the description sufficiently conveys the tool's behavioral profile for a simple, safe operation.

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 of nine words. Every word is essential, and there is no redundancy or irrelevant information.

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 tool with no parameters and a simple return of listening topics, the description fully captures what the tool does and returns. No additional details are necessary for the agent to correctly invoke and interpret results.

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?

The input schema has no parameters, so schema description coverage is 100%. The description does not add parameter-level detail, but none is needed. Baseline score of 3 applies.

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 uses the clear verb 'List' and specifies the resource 'listening topics'. It distinctly separates this tool from siblings such as get_listening_topic_messages and get_listening_topic_metrics, which deal with messages and metrics rather than topics.

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 is provided on when to use this tool versus its siblings, nor are any prerequisites or contextual hints given. The description lacks explicit direction for appropriate usage scenarios.

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