Skip to main content
Glama
AudienseCo

Audiense Insights MCP Server

Official
by AudienseCo

get-report-info

Retrieve intelligence report details including status, segmentation, audience size, and access links from Audiense Insights to analyze marketing data.

Instructions

Retrieves detailed information about a specific intelligence report, including its status, segmentation type, audience size, segments, and access links.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
report_idYesThe ID of the intelligence report.

Implementation Reference

  • MCP tool handler that invokes getReportInfo, handles errors, pending status, and formats the response as JSON text.
    async ({ report_id }) => {
        const data = await getReportInfo(report_id);
    
        if (!data) {
            return {
                content: [
                    {
                        type: "text",
                        text: `Failed to retrieve report info for ID: ${report_id}.`,
                    },
                ],
            };
        }
    
        if (data.status === "pending") {
            return {
                content: [
                    {
                        type: "text",
                        text: `Report ${report_id} is still processing. Try again later.`,
                    },
                ],
            };
        }
    
        return {
            content: [
                {
                    type: "text",
                    text: JSON.stringify(data, null, 2)
                }
            ]
        };
    }
  • Zod input schema defining the required 'report_id' parameter.
    {
        report_id: z.string().describe("The ID of the intelligence report."),
    },
  • src/index.ts:53-93 (registration)
    Registers the 'get-report-info' MCP tool with server, including name, description, schema, and handler.
    server.tool(
        "get-report-info",
        "Retrieves detailed information about a specific intelligence report, including its status, segmentation type, audience size, segments, and access links.",
        {
            report_id: z.string().describe("The ID of the intelligence report."),
        },
        async ({ report_id }) => {
            const data = await getReportInfo(report_id);
    
            if (!data) {
                return {
                    content: [
                        {
                            type: "text",
                            text: `Failed to retrieve report info for ID: ${report_id}.`,
                        },
                    ],
                };
            }
    
            if (data.status === "pending") {
                return {
                    content: [
                        {
                            type: "text",
                            text: `Report ${report_id} is still processing. Try again later.`,
                        },
                    ],
                };
            }
    
            return {
                content: [
                    {
                        type: "text",
                        text: JSON.stringify(data, null, 2)
                    }
                ]
            };
        }
    );
  • Core helper function that performs the authenticated API request to retrieve specific report information.
    export async function getReportInfo(report_id: string): Promise<ReportInfoResponse | null> {
        return makeAudienseRequest<ReportInfoResponse>(`/reports/intelligence/${report_id}`);
    }
  • TypeScript interface defining the structure of the report info response data.
    export type ReportInfoResponse = {
        title: string;
        status: string;
        segmentation_type: string;
        full_audience?: { 
            size?: number;
            audience_influencers_id?: string;
        };
        segments?: { 
            id: string; 
            title: string; 
            size: number;
            audience_influencers_id?: string;
        }[];
        audience_influencers_id?: string;
        public: boolean;
        links?: { app?: string; public?: string };
        errors?: string[];
    };
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It states 'Retrieves' (implying a read operation) but doesn't disclose behavioral traits such as authentication needs, rate limits, error conditions, or what happens if the report_id is invalid. For a tool with no annotations, this leaves significant gaps in understanding its behavior.

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, efficient sentence that front-loads the purpose and lists key attributes without waste. Every word contributes to understanding the tool's function, making it appropriately sized and well-structured.

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 the tool's complexity (simple read operation with one parameter), no annotations, and no output schema, the description is adequate but incomplete. It covers the purpose and attributes but lacks behavioral details and output information, which are needed for full contextual understanding in the absence of structured data.

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 the single parameter 'report_id' fully documented in the schema. The description adds no additional meaning beyond what the schema provides, such as format examples or constraints, so it meets the baseline for high schema coverage without compensating value.

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 clearly states the verb 'Retrieves' and the resource 'detailed information about a specific intelligence report', with specific attributes listed (status, segmentation type, audience size, segments, access links). It distinguishes from siblings like 'get-reports' (likely listing reports) and 'report-summary' (likely providing summaries).

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 like 'get-reports' or 'report-summary' is provided. The description implies usage for a specific report but doesn't specify prerequisites or exclusions, leaving the agent to infer context from tool names alone.

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