Skip to main content
Glama

news_search

Search for recent news articles by entering a query to retrieve updated and relevant information using You.com's News API.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesThe news query to send to You.com's News API

Implementation Reference

  • src/index.ts:112-137 (registration)
    MCP server.tool registration for the 'news_search' tool, including input schema (query: string) and handler function that delegates to youClient.getNews(query), formats results as JSON text or error response.
    server.tool(
      "news_search",
      {
        query: z.string().describe("The news query to send to You.com's News API")
      },
      async ({ query }: { query: string }) => {
        try {
          const results = await youClient.getNews(query);
          return {
            content: [{ 
              type: "text", 
              text: JSON.stringify(results, null, 2)
            }]
          };
        } catch (error) {
          console.error("News search error:", error);
          return {
            content: [{ 
              type: "text", 
              text: `Error performing news search: ${error instanceof Error ? error.message : String(error)}` 
            }],
            isError: true
          };
        }
      }
    );
  • Core implementation of news search in YouApiClient.getNews: makes HTTP GET request to You.com News API endpoint with query param, returns the full response data.
    async getNews(query: string): Promise<any> {
      try {
        // Following the example exactly
        const params = { query };
        
        // Use the full URL format to match the Python example
        const response = await this.searchClient.get(`/news?query=${encodeURIComponent(query)}`, { params });
        
        // Return the complete response data to match the Python example
        return response.data;
      } catch (error) {
        console.error('Error in You.com news API call:', error);
        throw error;
      }
    }
Behavior1/5

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

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

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

Completeness1/5

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

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

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/jimbul/youdotcom_MCP'

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