Skip to main content
Glama
AudienseCo

Audiense Insights MCP Server

Official
by AudienseCo

get-reports

Retrieve your Audiense Insights reports to access audience data, demographics, and marketing insights for analysis.

Instructions

Retrieves the list of Audiense insights reports owned by the authenticated user.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler function that fetches intelligence reports via getIntelligenceReports and returns formatted JSON response or error message.
    async () => {
        const data = await getIntelligenceReports();
    
        if (!data) {
            return {
                content: [
                    {
                        type: "text",
                        text: "Failed to retrieve intelligence reports.",
                    },
                ],
            };
        }
    
        return {
            content: [
                {
                    type: "text",
                    text: JSON.stringify(data, null, 2)
                },
            ],
        };
    }
  • src/index.ts:22-48 (registration)
    Registration of the 'get-reports' MCP tool with server.tool, including description, empty input schema, and inline handler.
        "get-reports",
        "Retrieves the list of Audiense insights reports owned by the authenticated user.",
        {},
        async () => {
            const data = await getIntelligenceReports();
    
            if (!data) {
                return {
                    content: [
                        {
                            type: "text",
                            text: "Failed to retrieve intelligence reports.",
                        },
                    ],
                };
            }
    
            return {
                content: [
                    {
                        type: "text",
                        text: JSON.stringify(data, null, 2)
                    },
                ],
            };
        }
    );
  • Helper function getIntelligenceReports that performs the authenticated API call to retrieve the list of intelligence reports from Audiense.
    export async function getIntelligenceReports(): Promise<IntelligenceReportsResponse | null> {
        return makeAudienseRequest<IntelligenceReportsResponse>("/reports/intelligence");
    }
Behavior2/5

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

No annotations are provided, so the description carries full burden. It mentions 'authenticated user' (implying auth needs) but doesn't disclose other behavioral traits like whether it's read-only (implied by 'Retrieves'), rate limits, pagination, sorting, or what happens if no reports exist. For a tool with zero annotation coverage, this is a significant gap.

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 a single, efficient sentence that front-loads the core purpose. It could be slightly more structured by adding usage context, but it avoids redundancy and wastes no words.

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?

Given 0 parameters and no output schema, the description is minimally adequate but lacks completeness. It doesn't explain return values (e.g., format, fields) or behavioral details like pagination. For a list-retrieval tool with no annotations, more context on output and constraints would improve completeness.

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?

The tool has 0 parameters with 100% schema description coverage, so the schema fully documents the lack of inputs. The description adds no parameter information, which is appropriate here. Baseline is 4 for 0 parameters, as no additional semantics are needed.

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 action ('Retrieves') and resource ('list of Audiense insights reports'), specifying ownership scope ('owned by the authenticated user'). It distinguishes from some siblings like 'get-report-info' (detailed info vs. list) but doesn't explicitly differentiate from 'get-audience-insights' or 'report-summary', which might have overlapping purposes.

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 alternatives like 'get-report-info' (for detailed report data) or 'get-audience-insights' (possibly for broader insights). The description implies it's for listing reports, but lacks explicit when/when-not instructions or prerequisite context.

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