mcp
Server Details
Manage 230M+ influencers, track campaigns, and access real-time CIMS analytics via AI agents
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Score is being calculated. Check back soon.
Available Tools
2 toolsget_creatorARead-onlyIdempotentInspect
Retrieves a creator's profile and performance statistics including followers, average views, view rates, engagements, engagement rate, average likes, comments, shares, and saves. Looks up the creator by their social media handle and platform type. If the creator is not yet in the database but exists on a supported platform (Instagram, TikTok, YouTube), it will be discovered and saved automatically.
| Name | Required | Description | Default |
|---|---|---|---|
| handle | Yes | Social media handle of the creator (e.g. @username) | |
| platform | No | Platform filter. Required if handle is used to disambiguate between platforms. | |
| creatorId | No | Direct lookup by creator ID |
Tool Definition Quality
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, and openWorldHint=false. The description adds valuable behavioral context beyond annotations: the automatic discovery and saving of new creators, which is a significant side effect not captured in structured fields. No contradiction with annotations exists.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is efficiently structured in two sentences: the first states the core retrieval purpose and data returned, the second explains the lookup mechanism and automatic discovery feature. Every sentence earns its place with no wasted words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a read-only tool with good annotations but no output schema, the description provides solid context about what data is returned and the automatic discovery behavior. It could be more complete by mentioning response format or error conditions, but covers the essential usage scenario well.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
With 100% schema description coverage, the schema already documents all three parameters thoroughly. The description mentions 'handle' and 'platform type' but doesn't add meaningful semantic context beyond what's in the schema descriptions. The baseline of 3 is appropriate when the schema does the heavy lifting.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool's purpose with specific verbs ('Retrieves', 'Looks up', 'discovered and saved') and resources ('creator's profile and performance statistics'). It distinguishes from the sibling 'get_creators' by focusing on a single creator lookup with automatic discovery capabilities, not just retrieval.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides clear context for when to use this tool: to retrieve a creator's profile and statistics by handle/platform, with automatic discovery for new creators. However, it doesn't explicitly state when NOT to use it or mention the sibling 'get_creators' as an alternative for multiple creators.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
get_creatorsBRead-onlyIdempotentInspect
Searches for social media creators by name, handle, or platform. Uses the discovery service to find creators.
| Name | Required | Description | Default |
|---|---|---|---|
| age | No | Age range. | |
| bio | No | Free text search within creator's bio. | |
| skip | No | Number of results to skip for pagination. Default: 0. | |
| saves | No | Average saves filter. Plain string value. | |
| views | No | Average views filter using NumberValue format. Supports operators: >=N, <=N, >N, <N, N (equals), or range MIN-MAX (e.g. '>=1000', '<50000'). | |
| active | No | Activity recency filter using NumberValue format. Value represents years (e.g. '>=1' means active within last 1 year). Supports operators: >=N, <=N, >N, <N, N (equals). | |
| gender | No | Gender filter. Supports numeric values (1=female, 2=male, 3=other) or string values ('female', 'male', 'other'). Uses NumberValue format: >=, <=, >, <, = operators (e.g. '1', 'female'). | |
| growth | No | Growth filter using NumberValue format. Supports operators: >=N, <=N, >N, <N, N (equals), or range MIN-MAX. | |
| shares | No | Average shares filter. Plain string value. | |
| follower | No | Follower count filter using NumberValue format. Supports operators: >=N, <=N, >N, <N, N (equals), or range MIN-MAX (e.g. '>=10000', '<=100000', '>5000'). | |
| hashtags | No | Hashtags to filter by. Plain string values without # prefix. Combined total of mentions + hashtags cannot exceed 20. | |
| keywords | No | Content/Caption keywords to filter by. Plain string values (3+ chars). Words starting with @ or # are excluded. | |
| language | No | Language codes to filter by. Plain string values (e.g. 'en', 'sv'). | |
| mentions | No | Mentioned accounts to filter by. Plain string values without @ prefix. Combined total of mentions + hashtags cannot exceed 20. | |
| viewRate | No | View rate (views/followers) filter using NumberValue format. Supports operators: >=N, <=N, >N, <N, N (equals), or range MIN-MAX (e.g. '>=0.05', '<0.50'). | |
| lookalike | No | Lookalike profile names to filter by. Plain string values. | |
| sortField | No | Sort field . | |
| engagement | No | Engagement count filter using NumberValue format. Supports operators: >=N, <=N, >N, <N, N (equals), or range MIN-MAX (e.g. '>=500', '<10000'). | |
| lastPosted | No | Maximum number of days since last post. Must be >= 30 (e.g. '30', '90', '365'). | |
| audienceAge | No | Audience age filter. Supports GenderValue format: 'MM-MM gender OP value%' (e.g. '18-34 female>50%', '25-44 male>=30'), or StringValue format with weight: 'MM-MM>P%' (e.g. '13-64>0.01', '18-24>20%<80%'). | |
| withContact | No | Filter by contact availability (WithContactType enum). Repeat query parameter to pass multiple values. | |
| identityType | No | Platform. Repeat query parameter to pass multiple values. | |
| partnerships | No | Has sponsored posts with at least one of these brands. Plain string values. | |
| audienceBrand | No | Audience brand affinity filter using StringValue format. Supports weight thresholds: 'VALUE', 'VALUE>P%', 'VALUE<P%', 'VALUE>P%<P%'. Percentages are converted to decimals. | |
| sortDirection | No | Sort direction. Default: 'desc'. | |
| audienceGender | No | Audience gender filter using StringValue format. Supports weight thresholds: 'VALUE', 'VALUE>P%', 'VALUE<P%', 'VALUE>P%<P%' (e.g. 'female>60%', 'male>40%<90%'). Percentages are converted to decimals. | |
| engagementRate | No | Engagement rate filter using NumberValue format. Supports operators: >=N, <=N, >N, <N, N (equals), or range MIN-MAX (e.g. '>=0.03', '<0.10'). | |
| followersGrowth | No | Followers growth rate filter. Plain string value. | |
| profileLocation | No | Profile location filter using GeoLocationValue format: '(City,Country)' or '(City,Country)OP value' (e.g. '(,SE)', '(,AO)', '(Stockholm,SE)>=0.1'). Repeat query parameter to pass multiple values. | |
| audienceLanguage | No | Audience language filter using StringValue format. Supports weight thresholds: 'VALUE', 'VALUE>P%', 'VALUE<P%', 'VALUE>P%<P%' (e.g. 'en>50%'). Percentages are converted to decimals. | |
| audienceLocation | No | Audience location filter using GeoLocationValue format: '(City,Country)OP value' (e.g. '(,AS)>0.5', '(,AD)>0.5', '(Copenhagen,DK)>=0.1'). Repeat query parameter to pass multiple values. | |
| audienceLookalike | No | Audience lookalike filter using StringValue format. Supports weight thresholds: 'VALUE', 'VALUE>P%', 'VALUE<P%', 'VALUE>P%<P%'. Percentages are converted to decimals. | |
| audienceRelevance | No | Audience relevance filter using StringValue format. Supports weight thresholds: 'VALUE', 'VALUE>P%', 'VALUE<P%', 'VALUE>P%<P%'. Percentages are converted to decimals. |
Tool Definition Quality
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=true, and idempotentHint=true, covering safety and idempotency. The description adds minimal behavioral context: 'Uses the discovery service to find creators' implies it's a search operation, but doesn't disclose rate limits, pagination details (beyond the 'skip' parameter), or response format. With annotations doing heavy lifting, the description adds some value but lacks rich behavioral disclosure.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two concise sentences that state the core functionality and service used. It's front-loaded with the main purpose and avoids unnecessary details. However, it could be slightly more structured by explicitly mentioning filtering capabilities or sibling differentiation.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's complexity (33 parameters, no output schema) and rich annotations, the description is minimally adequate. It covers the basic purpose but lacks details on output format, pagination behavior, or error handling. With annotations providing safety and idempotency, the description meets a baseline but doesn't fully compensate for the missing output schema.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so the schema fully documents all 33 parameters. The description mentions search criteria ('by name, handle, or platform'), which aligns with some parameters but doesn't add meaningful semantics beyond what the schema provides. Baseline 3 is appropriate when schema coverage is high.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool's purpose: 'Searches for social media creators by name, handle, or platform.' It specifies the verb ('searches'), resource ('social media creators'), and search criteria. However, it doesn't explicitly differentiate from its sibling tool 'get_creator' (which likely retrieves a single creator), so it misses full sibling distinction.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
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. It mentions 'Uses the discovery service to find creators,' which hints at context but doesn't specify when to choose this over 'get_creator' or other search methods. No explicit when/when-not statements or prerequisites are included.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail — every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control — enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management — store and rotate API keys and OAuth tokens in one place
Change alerts — get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption — public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics — see which tools are being used most, helping you prioritize development and documentation
Direct user feedback — users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!