F
licenseNot graded
qualityC
maintenanceEnables Claude to pull exact YouTube creator stats (subscribers, views, engagement) and discover new creators, then write them into a Notion Influencers roster.
-
intelligence
Server Details
Agent-callable creator intelligence: 952+ scored YouTube creators across 180 niches.
If you are the author of this connector, you can claim ownership with GitHub, an HTTP challenge, or a DNS record. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- byimprint/mcp-server
- GitHub Stars
- 0
- Server Listing
- @byimprint/mcp-server
Available Tools
2 toolsbyimprint-site-indexbyImprint public site indexARead-onlyIdempotentInspect
Return canonical public service, evidence, legal, developer, and machine-readable URLs for byImprint.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
Output Schema
ParametersJSON Schema
| Name | Required | Description |
|---|---|---|
| markdown | Yes | Current public byImprint guidance in Markdown. |
TDQS
A4/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already carry the safety profile (readOnlyHint=true, idempotentHint=true, destructiveHint=false), so the description's burden is lighter. It adds a mild behavioral nuance with 'canonical,' indicating the returned set is curated and authoritative rather than arbitrary, which aligns with the read-only annotation. No contradiction exists, but no additional behavioral detail (e.g., format, ordering) is disclosed.
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 entire description is a single front-loaded sentence beginning with the imperative verb 'Return,' followed by a compact enumeration of URL categories. There is zero filler or repetition, and the length is proportionate to the tool's simplicity.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness4/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a zero-parameter lookup tool, the definition is nearly complete: annotations cover the safety profile, an output schema exists to document return values, and the description states the tool's purpose. The only gap is that it does not reference the sibling byimprint-when-to-use to help the agent choose between them, though this is a minor omission for such a simple tool.
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 zero parameters and an empty schema, so there is nothing for the description to document on inputs. Per the rubric, a 0-param tool earns a baseline of 4, and the description sensibly focuses on the output nature instead of inventing parameter details.
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 uses a specific verb ('Return') and a clearly defined resource: 'canonical public service, evidence, legal, developer, and machine-readable URLs for byImprint.' It enumerates the URL categories, making the tool's scope concrete and distinguishable from the sibling byimprint-when-to-use, which presumably provides usage guidance rather than a URL index.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines3/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
Usage context is only implied: an agent can infer that this tool is for when canonical byImprint URLs are needed, but the description never states when to use it or when to prefer the sibling byimprint-when-to-use. There is no explicit exclusion or alternative routing, so the agent must reason from the purpose alone.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
byimprint-when-to-useWhen to use byImprintARead-onlyIdempotentInspect
Return current, bounded guidance for deciding when byImprint fits an owner-led business.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
Output Schema
ParametersJSON Schema
| Name | Required | Description |
|---|---|---|
| markdown | Yes | Current public byImprint guidance in Markdown. |
TDQS
A4/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already establish readOnlyHint and idempotentHint, so the description's behavioral contribution is limited to labeling the output as 'current' and 'bounded' guidance. It does not describe the output format or maintenance behavior, but no side-effect disclosure is needed here.
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, front-loaded sentence with no filler. Every phrase ('current,' 'bounded,' 'owner-led business') contributes to the agent's understanding, making it appropriately concise without becoming vague.
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?
For a no-parameter, read-only tool with an output schema and safety annotations, the description is complete enough to invoke correctly. The purpose and scope are clear, and no additional setup, prerequisites, or side effects need to be disclosed.
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 accepts zero parameters, so the schema is trivially complete and there is no parameter meaning for the description to clarify. The baseline of 4 applies because there is nothing for parameters to add.
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 names a specific verb ('Return') and a resource: current, bounded guidance for deciding when byImprint fits an owner-led business. It clearly distinguishes the tool's purpose from a generic site index, though it does not explicitly contrast with the sibling tool.
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 for when to use the tool: when the agent needs to decide whether byImprint is appropriate for an owner-led business. It does not explicitly name alternatives or when-not-to-use conditions, so it stops short of full guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
9 tool updates
- Added
byimprint-site-index - Added
byimprint-when-to-use - Removed
imprint-filter - Removed
imprint-grep - Removed
imprint-map - Removed
imprint-niche - Removed
imprint-profile - Removed
imprint-rank-creators-for-brand - Removed
imprint-search
1 tool update
- Changed
imprint-rank-creators-for-brand1 field changed- added
Input schema / properties / sourceBackedMarketMapAdded value: +{ + "description": "Optional market-map baseline from web/source review. The ranker returns it beside the shortlist so agents can see obvious names, holds, exclusions, ingestion gaps, and supporting URLs.", + "items": { + "properties": { + "name": { + "description": "Creator, channel, or category authority name", + "type": "string" + }, + "reason": { + "description": "Brief-specific rationale for the disposition", + "type": "string" + }, + "slug": { + "description": "Imprint creator slug when the market-map entry exists in the catalog", + "type": "string" + }, + "sources": { + "description": "Public sources backing this disposition", + "items": { + "properties": { + "sourceType": { + "description": "Source kind, such as market-list or creator-profile", + "type": "string" + }, + "title": { + "description": "Source title", + "type": "string" + }, + "url": { + "description": "Source URL", + "format": "uri", + "type": "string" + }, + "use": { + "description": "How this source supports the market-map disposition", + "type": "string" + } + }, + "required": [ + "title", + "url" + ], + "type": "object" + }, + "type": "array" + }, + "status": { + "description": "Disposition such as recommend, hold, exclude, or source-backed-recommend-with-ingestion", + "type": "string" + } + }, + "required": [ + "name", + "status", + "reason" + ], + "type": "object" + }, + "maxItems": 50, + "type": "array" +}
1 tool update
- Changed
imprint-rank-creators-for-brand3 fields changed- added
Input schema / properties / additionalContextAdded value: +{ + "description": "Additional buyer constraints or context", + "type": "string" +} - changed
Input schema / properties / preferredPlatforms / items / enumPrevious value: -[ - "youtube", - "instagram", - "tiktok", - "blog", - "site", - "unknown" -]New value: +[ + "youtube", + "instagram", + "tiktok", + "newsletter", + "blog", + "site", + "unknown" +] - added
Input schema / properties / timelineAdded value: +{ + "description": "Campaign timing or launch window", + "type": "string" +}
7 tool updates
- First observed
imprint-filter - First observed
imprint-grep - First observed
imprint-map - First observed
imprint-niche - First observed
imprint-profile - First observed
imprint-rank-creators-for-brand - First observed
imprint-search
Frequently Asked Questions
Claiming proves that you control a remote MCP connector. It does not move, proxy, or interrupt the server.
Open the connector listing, choose Claim ownership, and sign in to Glama.
Complete one verification method:
GitHub identity — fastest for official registry listings. For a namespace such as
io.github.alice/server, link the matching GitHub user, then choose Claim with GitHub. An organization namespace such asio.github.acme/serveralso needs that organization to have installed the Glama AI GitHub App and approved its permissions, because GitHub discloses organization membership only to apps it has installed. Use HTTP or DNS when it has not.HTTP challenge — works when you can deploy a public file. Generate a token, publish the exact JSON Glama shows at
/.well-known/glama.jsonon the same origin as the connector, then choose Check HTTP challenge.DNS challenge — works when you control DNS but cannot change the server. Generate a token, create the exact TXT record Glama shows, wait for it to propagate, then choose Check DNS challenge.
After verification, Glama sends a confirmation email and gives you access to listing details, thumbnails, health checks, and analytics. Keep the HTTP file or DNS record in place: Glama periodically checks it and ownership remains verified while the token is discoverable.
The HTTP ownership file has this structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"claim": "glama_claim_..."
}Claim tokens are opaque, stable, and bound to the signed-in Glama account. They contain no email address or other personal information. If Glama can no longer discover a verified HTTP or DNS token, it starts a seven-day grace period before removing claim-based access. Restore the same token during that period to keep ownership verified. Never publish an email address, Glama session token, GitHub token, or connector credential as ownership proof.
If verification fails, confirm that you copied the current token exactly. The HTTP file must be public, return valid JSON with a successful HTTP response, and stay on the connector's origin. DNS changes may need more time to propagate. A claim cannot transfer to a different origin or hostname: if the connector target changes, Glama starts the grace period and the new target must be claimed separately after the previous claim is released.
For a connector linked to the official MCP Registry, registry updates continue to replace its name, description, and URL by default. After claiming, open Manage connector and enable Use Glama listing details as the source of truth if edits made on Glama should be preserved. Categories and thumbnails are always managed on Glama; registry linkage and technical connection settings continue to sync.
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
To improve your MCP server's ranking:
Claim ownership of the server listing
Complete the server profile with an accurate description and thumbnail
Provide a test profile so Glama can connect to and evaluate the server
Keep tool definitions clear and complete to earn a high Tool Definition Quality Score (TDQS)
Route real usage through the Glama Gateway; more recorded successful server uses also improve the ranking
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!
Related MCP Connectors
Creator discovery & analytics across YouTube, Instagram, TikTok (30M+) + brand/sponsor intel.
Find and analyze influencers with creator search, lookalikes, profiles, posts, and transcripts.
YouTube transcripts, search, channel/playlist listings and upload tracking for AI agents. No signup.
Public index of YouTube sponsorships: which brands sponsor which creators, from sampled videos.
Related MCP Servers
- AlicenseAqualityAmaintenanceEnables AI agents to search YouTube like a database, retrieve transcripts and channel data, and mine videos for claims, numbers, and demand signals — without needing an API key.6327MIT
Sponsorbook MCPofficial
AlicenseNot gradedqualityBmaintenanceEnables AI agents to research YouTube sponsors, inspect brands and their video evidence, explore overlapping creators and similar brands, manage research lists, and work with verified contacts.335MIT- FlicenseAqualityCmaintenanceEnables AI assistants to analyze YouTube channels, videos, transcripts, and content strategy through structured tool calls.1757-
Try in Browser
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
A3.9/5.0
Disambiguation4/5
The two tools have distinct purposes: one returns resource URLs while the other provides timing guidance. The shared imprint prefix is rather clear but the roles of site-index vs conditions would not be mixed because their descriptions are clearly different.
Naming Consistency5/5
Both tool names start with the lower-case 'byprint', followed by the hyphen and meaningful compound words ('site-index' and a suitable moment'). The hyphenated multiword style is uniform and predictable.
Tool Count3/5
With only two tools, the scope is tight: They target byprint's site index and the right time. For the 'intelligence' server this is skinny, though not trivial; two tools may be sufficient for narrow niche use-cases. This is on the borderline of a minimal set.
Completeness3/5
The server covers basic navigation (site URLs) and the timing aspect of byimprint. The gap is the absence of an explicit resource representation of byimprint's own-son or worse page, but the two tools cover the core. A limited index resource made up the remaining surface.