mcp-bluesky-brand-presence-mapper

Map Bluesky Brand Presence

map_bluesky_brand_presence

Read-onlyIdempotent

Find a company's official Bluesky account by its domain or handle, with exact follower, following, and post counts. Returns profile details or not_found if no account exists.

Instructions

Resolve a company domain, or a Bluesky handle, to that company's official Bluesky account through the public AT Protocol API. Returns the profile URL, handle, DID, exact follower, following and post counts, display name, bio and account creation date, as one flat Clay ready row. Counts are EXACT here, not rounded, unlike every other platform in this family. When the resolved handle IS the company domain, Bluesky granted it after a DNS check the company had to pass, and the row flags that as the strongest identity evidence available. A company with no Bluesky account returns not_found, which is a real and common answer. Read only; requires an APIFY_TOKEN and consumes Apify credits per call.

Input Schema

TableJSON Schema

Name	Required	Description
`handle`	No	Optional. A Bluesky handle such as shopify.com, mamba.bsky.social, or a did. Supplying it skips discovery entirely and goes straight to the profile fetch. A company that has verified its domain with Bluesky uses the bare domain as its handle, which is why this often equals company_domain.
`skipCache`	No	When "false" (default) a successful lookup is cached for seven days and reused. Set "true" to force a fresh fetch. Sent as a string for Clay compatibility.
`company_name`	No	Optional. Improves search accuracy and is what the identity gate checks a discovered profile against, so supplying it reduces wrong matches.
`company_domain`	No	Bare company domain, for example shopify.com. Supply this or a handle. With a domain the actor runs full discovery; with a handle it skips straight to the fetch.
`useActorSearch`	No	When "true" (default) and the domain is not itself a verified handle, Bluesky's own account search is used to find the company. Set "false" to rely only on the company homepage and the domain as handle, which avoids any chance of matching a similarly named account. Sent as a string for Clay compatibility.
`includeFollowerCounts`	No	When "true" (default) the profile page is fetched and the counts are extracted. Set "false" to resolve the profile URL only, which is cheaper and needs no proxy. Sent as a string for Clay compatibility.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Sep 8, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Annotations already mark the tool read-only, idempotent, and non-destructive. The description goes further by disclosing that it consumes Apify credits and requires an APIFY_TOKEN, that successful lookups are cached for seven days, that counts are exact rather than rounded, and that a missing Bluesky account returns not_found. No contradiction with annotations.

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 compact set of sentences, each earning its place: purpose, output shape, exactness caveat, DNS-evidence nuance, not_found expectation, and operational requirements. It is front-loaded with the core purpose and avoids nested jargon. Slightly dense but still efficient.

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?

With no output schema, the description compensates by enumerating the returned fields (profile URL, handle, DID, counts, display name, bio, creation date) and the flat row format. It also covers auth requirements, credit consumption, caching behavior, and the not_found outcome. For a read-only resolver with six fully documented optional parameters, this is complete enough for an agent to call it correctly.

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%, so the baseline is 3. The main description adds useful context about the DNS-check meaning when a handle equals the company domain, but the individual parameter meanings are already fully documented in the schema. The description does not materially improve parameter understanding beyond that.

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 opens with a specific verb, 'Resolve', names the exact resource (a company's official Bluesky account), and states the mechanism (public AT Protocol API). It further clarifies output contents and highlights that counts are exact 'unlike every other platform in this family,' giving the tool a clear identity even without sibling names.

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 provides contextual usage guidance: it explains when discovery runs versus when a handle skips straight to fetch, and it prepares the agent for a common not_found result. It does not name explicit alternatives or when-not-to-use conditions, but with no sibling tools present, the context is still clear and actionable.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools

map_bluesky_brand_presenceA