Skip to main content
Glama
tommysdaniel

InfluIQ MCP Server

by tommysdaniel

Start Influencer Analysis

influiq_start_analysis

Start an influencer analysis on YouTube or Instagram by providing a URL or username. Returns an analysis ID for polling results.

Instructions

Start a new influencer analysis on InfluIQ. Consumes 1 analysis credit.

Supports YouTube channels and Instagram profiles. Provide either a URL or a platform + username.

Returns an analysisId to poll for results with influiq_get_analysis.

Args:

  • platform: "youtube" or "instagram"

  • url: Full URL to the channel/profile (e.g. https://youtube.com/@MrBeast)

  • username: Channel handle or username (e.g. "MrBeast", "@MrBeast")

  • brand_profile_id: Optional brand profile ID for brand-fit scoring

Returns: { analysisId, status, platform, creditsRemaining }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
platformYesPlatform to analyze: "youtube" or "instagram"
urlNoFull URL to the channel or profile
usernameNoChannel handle or Instagram username
brand_profile_idNoBrand profile ID for brand-fit comparison
Behavior4/5

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

Beyond annotations (readOnlyHint=false, destructiveHint=false, idempotentHint=false, openWorldHint=true), the description adds that it consumes 1 analysis credit, supports only YouTube/Instagram, and returns an analysisId for polling. No contradictions.

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 well-structured: a concise introductory paragraph followed by a brief args list. Every sentence adds value, and the key information (purpose, credit cost, platforms, return value) is front-loaded.

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?

Despite no output schema, the description explicitly states the return structure (analysisId, status, platform, creditsRemaining). It covers all parameters, explains the workflow, and provides enough detail for an agent to use the tool correctly.

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?

Schema coverage is 100%, so the schema documents all parameters. The description adds value with examples (e.g., 'https://youtube.com/@MrBeast'), clarifies that username can include '@', and explains brand_profile_id is for brand-fit scoring. This supplements the schema.

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 it starts a new influencer analysis, specifies supported platforms (YouTube, Instagram), and explains how to provide input (URL or platform+username). It also distinguishes from siblings by mentioning the returned analysisId for polling with influiq_get_analysis.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives clear context on when to use: to start an analysis, consuming 1 credit, and that it returns an analysisId for polling. It does not explicitly state when not to use or direct to alternatives, but the context is sufficient for most agents.

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/tommysdaniel/influiq-mcp-server'

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