Skip to main content
Glama
brianellin

Bluesky MCP Server

by brianellin

search-feeds

Search for custom feeds on Bluesky using a specific query and limit results to streamline content discovery and access relevant posts efficiently.

Instructions

Search for custom feeds on Bluesky

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoNumber of results to fetch (1-100)
queryYesSearch query for finding feeds

Implementation Reference

  • Full implementation of the 'search-feeds' tool including registration, inline Zod input schema (query: string, limit: number 1-100 default 10), and handler logic that uses Bluesky's unspecced getPopularFeedGenerators API to search feeds, formats results as numbered list with name, URI, description, creator, likes, and handles errors.
      "search-feeds",
      "Search for custom feeds on Bluesky",
      {
        query: z.string().describe("Search query for finding feeds"),
        limit: z.number().min(1).max(100).default(10).describe("Number of results to fetch (1-100)"),
      },
      async ({ query, limit }) => {
        if (!agent) {
          return mcpErrorResponse("Not logged in. Please check your environment variables.");
        }
    
        try {
          const response = await agent.api.app.bsky.unspecced.getPopularFeedGenerators({ 
            query, 
            limit 
          });
          
          if (!response.success) {
            return mcpErrorResponse("Failed to search for feeds.");
          }
    
          const { feeds } = response.data;
          
          if (!feeds || feeds.length === 0) {
            return mcpSuccessResponse(`No feeds found for query: "${query}"`);
          }
    
          const results = feeds.map((feed: any, index: number) => {
            return `Feed #${index + 1}:
    Name: ${feed.displayName || 'Unnamed Feed'}
    URI: ${feed.uri}
    ${feed.description ? `Description: ${feed.description}` : ''}
    Creator: @${feed.creator.handle} ${feed.creator.displayName ? `(${feed.creator.displayName})` : ''}
    Likes: ${feed.likeCount || 0}
    ${feed.indexedAt ? `Indexed At: ${new Date(feed.indexedAt).toLocaleString()}` : ''}
    ---`;
          }).join("\n\n");
    
          return mcpSuccessResponse(results);
        } catch (error) {
          return mcpErrorResponse(`Error searching for feeds: ${error instanceof Error ? error.message : String(error)}`);
        }
      }
    );
Behavior2/5

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

With no annotations provided, the description carries full burden but only states the basic function. It doesn't disclose behavioral traits such as authentication requirements, rate limits, pagination, error handling, or what constitutes a 'custom feed' versus other feed types.

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 with zero wasted words. It's appropriately sized and front-loaded, directly stating the tool's purpose without unnecessary elaboration.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a search tool with no annotations and no output schema, the description is incomplete. It lacks context on authentication, result format, error cases, or how 'custom feeds' differ from other feeds, leaving significant gaps for an agent to use it effectively.

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 schema fully documents both parameters (query and limit). The description adds no additional meaning beyond what's in the schema, such as search syntax examples or result ordering, meeting the baseline for high coverage.

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 clearly states the action ('Search for') and resource ('custom feeds on Bluesky'), providing a specific purpose. However, it doesn't explicitly differentiate from sibling tools like 'search-people' or 'search-posts', which search for different resources on the same platform.

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 is provided on when to use this tool versus alternatives like 'get-pinned-feeds' or 'get-feed-posts'. The description implies usage for finding feeds via search but doesn't specify scenarios, prerequisites, or exclusions.

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

Related 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/brianellin/bsky-mcp-server'

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