Skip to main content
Glama
Decodo

Decodo MCP Server

bing_search

Read-only

Scrape and parse Bing search results with customizable geolocation, locale, device type, and pagination options.

Instructions

Scrape Bing Search results with automatic parsing

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesSearch query for Bing (e.g., "laptop")
geoNoGeolocation of the desired request, expressed as a country name
localeNoLocale of the desired request
jsRenderNoShould the request be opened in a headless browser, false by default
domainNoBing domain (e.g., bing.com, bing.co.uk)
deviceTypeNoDevice type to emulate for the request
pageFromNoStarting page number for pagination

Implementation Reference

  • The BingSearchTool class that implements the tool logic. The register() method (lines 31-71) contains the actual handler: it calls sapiClient.scrape() with target SCRAPER_API_TARGETS.BING_SEARCH, transforms the response by removing 'url' fields to reduce character count, and returns the scraped Bing search results as text content.
    export class BingSearchTool extends Tool {
      toolset = TOOLSET.SEARCH;
    
      private static FIELDS_WITH_HIGH_CHAR_COUNT = ['url'];
    
      transformResponse = ({ data }: { data: object }) => {
        for (const fieldToRemove of BingSearchTool.FIELDS_WITH_HIGH_CHAR_COUNT) {
          data = removeKeyFromNestedObject({ obj: data, keyToRemove: fieldToRemove });
        }
    
        return { data: JSON.stringify(data) };
      };
    
      register = ({ server, sapiClient, auth }: ToolRegistrationArgs) => {
        server.registerTool(
          'bing_search',
          {
            description: 'Scrape Bing Search results with automatic parsing',
            inputSchema: {
              query: z.string().describe('Search query for Bing (e.g., "laptop")'),
              geo: zodGeo,
              locale: zodLocale,
              jsRender: zodJsRender,
              domain: zodDomain,
              deviceType: zodDeviceType,
              pageFrom: zodPageFrom,
            },
            annotations: {
              readOnlyHint: true,
              openWorldHint: true,
            },
          },
          async (scrapingParams: ScrapingMCPParams, extra: ProgressExtra) => {
            const params = {
              ...scrapingParams,
              target: SCRAPER_API_TARGETS.BING_SEARCH,
              parse: true,
            } satisfies ScraperAPIParams;
    
            const { data } = await sapiClient.scrape<object>({ auth, scrapingParams: params, extra });
    
            const { data: text } = this.transformResponse({ data });
    
            return {
              content: [
                {
                  type: 'text',
                  text,
                },
              ],
            };
          }
        );
      };
    }
  • Input schema registration for 'bing_search'. Defines the input parameters: query (string), geo, locale, jsRender, domain (optional Bing domain), deviceType, and pageFrom (optional pagination start page). Annotations mark the tool as readOnlyHint and openWorldHint.
    register = ({ server, sapiClient, auth }: ToolRegistrationArgs) => {
      server.registerTool(
        'bing_search',
        {
          description: 'Scrape Bing Search results with automatic parsing',
          inputSchema: {
            query: z.string().describe('Search query for Bing (e.g., "laptop")'),
            geo: zodGeo,
            locale: zodLocale,
            jsRender: zodJsRender,
            domain: zodDomain,
            deviceType: zodDeviceType,
            pageFrom: zodPageFrom,
          },
          annotations: {
            readOnlyHint: true,
            openWorldHint: true,
          },
        },
  • Import of BingSearchTool in the server file.
    BingSearchTool,
  • BingSearchTool is instantiated and added to allTools array. It gets registered via tool.register() in registerAllTools() or registerTools() depending on toolset filtering.
    new BingSearchTool(),
  • Enum value BING_SEARCH = 'bing_search' in SCRAPER_API_TARGETS enum, used as the target parameter when making the scraping API call.
    BING_SEARCH = 'bing_search',
Behavior3/5

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

Annotations already indicate readOnly and openWorld hints; the description adds 'automatic parsing' but does not elaborate on behavior like result format, pagination, or error handling.

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 single front-loaded sentence with no waste, though it could benefit from a bit more structure without losing conciseness.

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?

No output schema exists, but the description does not explain what the parsed results look like, leaving a significant gap for an agent; given the tool's complexity (7 params), more completeness is needed.

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 coverage is 100% with clear descriptions for each parameter; the description adds minimal value beyond the schema, only mentioning 'automatic parsing' briefly.

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?

Description clearly states the tool scrapes Bing Search results with automatic parsing, using a specific verb and resource that distinguishes it from sibling search tools like google_search.

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 over alternatives like google_search or other search tools, and no conditions or exclusions are mentioned.

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

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/Decodo/mcp-server'

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