Skip to main content
Glama
ErickWendel

Erick Wendel Contributions MCP

by ErickWendel

get_videos

Retrieve videos from Erick Wendel's content library with filtering by ID, title, or language and pagination controls for efficient browsing.

Instructions

Get a list of videos with optional filtering and pagination.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoFilter videos by ID
titleNoFilter videos by title
languageNoFilter videos by language
skipNoNumber of videos to skip
limitNoMaximum number of videos to return

Implementation Reference

  • The main handler function for the 'get_videos' tool. It fetches videos using the fetchVideos service, formats the result as a JSON text response, and handles errors.
    handler: async (params: VideosParams): Promise<McpResponse> => {
      try {
        const result = await fetchVideos(params);
    
        if (!result.getVideos) {
          throw new Error('No results returned from API');
        }
    
        const content: McpTextContent = {
          type: "text",
          text: `Videos Results:\n\n${JSON.stringify(result.getVideos, null, 2)}`
        };
    
        return {
          content: [content],
        };
      } catch (error) {
        throw new Error(`Failed to fetch videos: ${error.message}`);
      }
    }
  • Zod schema defining the input parameters for the get_videos tool.
    parameters: {
      id: z.string().optional().describe("Filter videos by ID"),
      title: z.string().optional().describe("Filter videos by title"),
      language: z.string().optional().describe("Filter videos by language"),
      skip: z.number().optional().default(0).describe("Number of videos to skip"),
      limit: z.number().optional().default(10).describe("Maximum number of videos to return"),
    },
  • src/index.ts:35-40 (registration)
    Registration of the getVideosTool (named 'get_videos') with the MCP server.
    server.tool(
      getVideosTool.name,
      getVideosTool.description,
      getVideosTool.parameters,
      getVideosTool.handler
    );
  • Helper function that performs the actual GraphQL query to fetch videos from the API.
    export async function fetchVideos(params: {
      id?: string;
      title?: string;
      language?: string;
      skip?: number;
      limit?: number;
    }): Promise<VideosResponse> {
      const { id, title, language, skip, limit } = params;
      const languageCode = getLanguageCode(language);
    
      return await client.query({
        getVideos: {
          __args: {
            _id: id,
            title,
            language: languageCode,
            skip,
            limit,
          },
          totalCount: true,
          retrieved: true,
          processedIn: true,
          videos: {
            _id: true,
            title: true,
            abstract: true,
            type: true,
            link: true,
            additionalLinks: true,
            tags: true,
            language: true,
            date: true,
          },
        },
      }) as VideosResponse;
    }
  • Configuration defining the name and description of the get_videos tool.
    videos: {
      name: "get_videos",
      description: "Get a list of videos with optional filtering and pagination."
    },
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions filtering and pagination but fails to describe critical behaviors like whether this is a read-only operation, what permissions are needed, rate limits, error handling, or the format of returned data. For a tool with 5 parameters and no annotations, this is inadequate.

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 that front-loads the core purpose ('Get a list of videos') and adds key features ('with optional filtering and pagination') without any wasted words. It's appropriately sized for the tool's complexity.

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?

Given the tool's moderate complexity (5 parameters, no annotations, no output schema), the description is insufficient. It lacks details on behavioral traits, output format, error conditions, and differentiation from siblings. While the schema covers parameters well, the description doesn't compensate for missing annotations and output schema, leaving the agent with incomplete context.

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?

The description adds minimal value beyond the input schema, which has 100% coverage with clear parameter descriptions. It mentions 'optional filtering and pagination' which aligns with parameters like 'id', 'title', 'language', 'skip', and 'limit', but doesn't provide additional semantic context or usage examples. Baseline 3 is appropriate given the schema's thoroughness.

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 ('Get a list of videos') and resource ('videos'), making the purpose understandable. However, it doesn't distinguish this tool from potential siblings like 'get_posts' or 'get_talks' beyond the resource type, which prevents a perfect score.

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?

The description mentions 'optional filtering and pagination' which implies some usage context, but provides no explicit guidance on when to use this tool versus alternatives like 'get_posts' or 'get_talks', nor any prerequisites or exclusions. This leaves significant gaps in usage direction.

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/ErickWendel/erickwendel-contributions-mcp'

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