Skip to main content
Glama
mambalabsdev

mcp-page-finder-extractor

by mambalabsdev

Find Company Page

find_company_page
Read-onlyIdempotent

Locate a specified page type (pricing, careers, etc.) on a company's own website from its domain. Returns the URL, discovery method, and confidence score; optionally extracts structured data.

Instructions

Give it a company domain and name a page type. It finds that page on the company's own website and returns the URL, the method that found it, and a confidence for THAT method. 46 page types are available: pricing, investor_relations, security_trust_center, careers, about, contact, terms_of_service, privacy_policy, partners, integrations, documentation, api_reference, status_page, changelog, press_newsroom, customers_logos, sustainability_esg and 29 more. Discovery reads the homepage and footer link graph, the sitemap and its shards, known third party hosts such as boards.greenhouse.io and statuspage.io, and anchor vocabulary in 11 European languages; guessing a URL path is the LAST method tried and is scored 0.6 or below. Read {type}_confidence and threshold at 0.8 for anything a customer will see, and read coverage and fetch_status before trusting a false: found=false means the site was read and the page is not there, found=null means not enough was readable to say, and the two are never collapsed. Set mode to locate_and_extract to also read the page and return structured fields, which costs an extra event per page. Every input returns exactly one row, including the empty ones. Requires an APIFY_TOKEN and consumes Apify credits. Read only.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeNolocate returns the page URL, the method and a confidence. locate_and_extract also reads the page and returns structured fields into a second findings dataset. Default: "locate".
domainNoA single company domain, for example stripe.com. Protocol and path are stripped. Supply this or domains or companies.
domainsNoSeveral company domains. Every one returns a row, including the ones where nothing is found.
companiesNoCompanies you have a name for but not a domain. Identity resolution runs first on this path and is charged as its own event. Use domains instead whenever you hold a domain.
knownUrlsNoURLs you already hold, keyed by page type, for example {"pricing": "https://stripe.com/pricing"}. Discovery is skipped for that page type, which is faster and exact.
pageTypesNoWhich page types to locate. Each one costs a locate event and adds requests, so ask for what you will use. Default: ["pricing"].
skipCacheNofalse uses the 14 day cache. true forces a fresh crawl. Default: "false".
allowRenderNotrue opens a browser for pages that serve no readable HTML, which is most Nordic investor calendars. A browser is never used against a block, a CAPTCHA, a login or robots.txt. Default: "true".
concurrencyNoHow many companies to work on at once. Per company the actor is still strictly one request at a time with a delay, so this does not make it impolite to any single site. Sent as a string. Default: "10".
languageHintsNoLanguage codes to try first, for example ["de","fr"]. Vocabulary is multilingual by default in all 11 languages; this only reorders it and never shortens it.
maxPagesPerTypeNoBetween 1 and 12. Candidate pages opened per page type before giving up. Lowering it is faster and finds less. Sent as a string so it works from Clay. Default: "4".
extractionFieldsNoThe page agnostic extraction menu, available on any page type. Only used in locate_and_extract mode. Omit for all of them.
maxRequestsPerInputNoBetween 5 and 200. Hard ceiling on requests to one company's site. Hitting it returns coverage partial rather than a false negative. Sent as a string. Default: "60".
extractPageTypeFieldsNotrue also runs the field map bound to the page type: pricing plans, filing rows and a derived fiscal year end, certifications, ATS host, governing law. Only used in locate_and_extract mode. Default: "true".
Behavior5/5

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

Annotations already declare readOnly/openWorld/idempotent, and the description builds substantially on them: discovery method order, 'guessing a URL path is the LAST method tried and is scored 0.6 or below,' found=false vs null semantics, browser never used against blocks/CAPTCHAs, one row per input, APIFY_TOKEN and credit consumption. This is exemplary behavioral disclosure.

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 long but information-dense and front-loaded. The opening sentence states core behavior, and every subsequent sentence adds load-bearing operational detail: available page types, discovery heuristics, confidence thresholds, output semantics, costs, and auth. No wasted words.

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

Completeness4/5

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

Given the tool's complexity (14 params, no output schema), the description covers the key behavioral context: return values (URL, method, confidence), interpretations of found=false/null, coverage/fetch_status, and what locate_and_extract adds. It doesn't enumerate all response fields, but it describes the critical ones sufficiently.

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 all 14 parameters documented, so baseline is 3. The description adds contextual meaning (mode costs extra events, companies path runs identity resolution, knownUrls skips discovery) but does not need to re-explain parameter syntax since the schema already does that thoroughly.

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 first sentence is a specific verb+resource: 'Give it a company domain and name a page type. It finds that page on the company's own website and returns the URL, the method, and a confidence.' This unambiguously states what the tool does and distinguishes it from generic web search even without sibling tools.

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 clear context: when to use locate vs locate_and_extract, 'Use domains instead whenever you hold a domain,' 'ask for what you will use' for pageTypes, and knownUrls to skip discovery. No explicit exclusions or alternatives are needed since there are no sibling tools, but the guidance is strong.

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/mambalabsdev/mcp-page-finder-extractor'

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