Skip to main content
Glama
AudienseCo

Audiense Insights MCP Server

Official
by AudienseCo

get-audience-content

Analyze audience content engagement by retrieving detailed breakdowns of liked, shared, and influential content including posts, domains, hashtags, and media.

Instructions

Retrieves audience content engagement details for a given audience.

This tool provides a detailed breakdown of the content an audience interacts with, including:

  • Liked Content: Popular posts, top domains, top emojis, top hashtags, top links, top media, and a word cloud.

  • Shared Content: Content that the audience shares, categorized similarly to liked content.

  • Influential Content: Content from influential accounts that impact the audience, with similar categorization.

Each category contains:

  • popularPost: List of the most engaged posts.

  • topDomains: Most mentioned domains.

  • topEmojis: Most used emojis.

  • topHashtags: Most used hashtags.

  • topLinks: Most shared links.

  • topMedia: Media types shared and samples.

  • wordcloud: Frequently used words.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
audience_content_idYesThe ID of the audience content to retrieve.

Implementation Reference

  • src/index.ts:259-302 (registration)
    Registers the 'get-audience-content' MCP tool with description, Zod input schema, and handler function that calls getAudienceContent and formats response.
    server.tool(
        "get-audience-content",
        `Retrieves audience content engagement details for a given audience.
    
    This tool provides a detailed breakdown of the content an audience interacts with, including:
    - **Liked Content**: Popular posts, top domains, top emojis, top hashtags, top links, top media, and a word cloud.
    - **Shared Content**: Content that the audience shares, categorized similarly to liked content.
    - **Influential Content**: Content from influential accounts that impact the audience, with similar categorization.
    
    Each category contains:
    - **popularPost**: List of the most engaged posts.
    - **topDomains**: Most mentioned domains.
    - **topEmojis**: Most used emojis.
    - **topHashtags**: Most used hashtags.
    - **topLinks**: Most shared links.
    - **topMedia**: Media types shared and samples.
    - **wordcloud**: Frequently used words.`,
        {
            audience_content_id: z.string().describe("The ID of the audience content to retrieve."),
        },
        async ({ audience_content_id }) => {
            const data = await getAudienceContent(audience_content_id);
    
            if (!data) {
                return {
                    content: [
                        {
                            type: "text",
                            text: `No content found for audience ${audience_content_id}.`,
                        },
                    ],
                };
            }
    
            return {
                content: [
                    {
                        type: "text",
                        text: JSON.stringify(data, null, 2),
                    },
                ],
            };
        }
    );
  • MCP handler function for 'get-audience-content' tool that fetches data via getAudienceContent and returns formatted JSON response.
    async ({ audience_content_id }) => {
        const data = await getAudienceContent(audience_content_id);
    
        if (!data) {
            return {
                content: [
                    {
                        type: "text",
                        text: `No content found for audience ${audience_content_id}.`,
                    },
                ],
            };
        }
    
        return {
            content: [
                {
                    type: "text",
                    text: JSON.stringify(data, null, 2),
                },
            ],
        };
    }
  • Zod input schema defining the required 'audience_content_id' parameter for the tool.
    {
        audience_content_id: z.string().describe("The ID of the audience content to retrieve."),
    },
  • Helper function implementing the core API call to Audiense for retrieving audience content details using authenticated request.
     * Retrieves the relevant content that an audience engages with.
     */
    export async function getAudienceContent(audience_content_id: string): Promise<{
        createdAt: string;
        startDate: string;
        endDate: string;
        status: string;
        likedContent: any;
        sharedContent: any;
        influentialContent: any;
    } | null> {
        return makeAudienseRequest<{
            createdAt: string;
            startDate: string;
            endDate: string;
            status: string;
            likedContent: any;
            sharedContent: any;
            influentialContent: any;
        }>(`/audience_content/${audience_content_id}`);
    }
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It describes what data is returned (content breakdowns) but doesn't mention critical behavioral aspects like whether this is a read-only operation, potential rate limits, authentication requirements, error conditions, or data freshness. The description focuses on output structure rather than operational behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured with clear bullet points and categorization. It's appropriately sized for the complexity of the tool, though the detailed breakdown of return categories could be considered slightly verbose. The information is front-loaded with the core purpose stated first.

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

Completeness3/5

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

For a tool with no annotations and no output schema, the description provides good detail about what data is returned but lacks operational context. It adequately describes the output structure but doesn't cover behavioral aspects or usage guidance. Given the single parameter with full schema coverage, the description is moderately complete but has significant gaps in behavioral transparency.

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?

Schema description coverage is 100% with one parameter clearly documented. The description doesn't add any parameter-specific information beyond what's in the schema, but with complete schema coverage, the baseline score of 3 is appropriate. No additional semantic context is provided about the 'audience_content_id' parameter.

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's purpose as retrieving audience content engagement details with a breakdown of liked, shared, and influential content. It specifies the resource (audience content) and verb (retrieves), but doesn't explicitly differentiate from sibling tools like 'get-audience-insights' or 'get-reports' which might have overlapping functionality.

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?

The description provides no guidance on when to use this tool versus alternatives like 'get-audience-insights' or 'get-reports'. It doesn't mention prerequisites, exclusions, or specific scenarios where this tool is preferred over sibling tools, leaving the agent without contextual usage direction.

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/AudienseCo/mcp-audiense-insights'

If you have feedback or need assistance with the MCP directory API, please join our Discord server