Skip to main content
Glama
460,228 tools. Updated 2026-08-17 19:39

"Request for Full Article Crawling Information" matching MCP tools:

  • Get bias analysis for a specific article by its URL. Use this when you have a direct link to an article and want to know its political leaning, credibility, emotionality, and other bias dimensions — without needing to know the source name first. On success (found=true), returns: - article_id, classification_id, requested_url, matched_url, title, source, date, link, category - teaser: article excerpt - summary: one-sentence AI summary - context: AI-generated context for the article - implicit_assumptions: tacit or unstated premises the article's claims or framing rely on (list of concise strings, when available) - extracted_data: structured quantitative/qualitative facts extracted from the article - raw_data: legacy serialized form of extracted_data - bias_description: narrative description of this specific article's bias - bias_values: dict of per-dimension article scores using canonical plain-text keys, e.g. {"liberal conservative bias": 4, "overall credibility": 7, "emotional bias": -5, ...} Article scores use -10 to +10 for bipolar dimensions and 0 to 10 for unipolar dimensions. Positive values lean toward the second pole of each dimension (conservative, authoritarian, etc.). - bias_analysis_status: 'evidence_ready', 'evidence_unverified', 'evidence_partial', 'scored_legacy', or 'pending' - bias_dimensions when include_evidence=true: each dimension's score, scale, evidence status, claim, verbatim evidence, counterevidence, confidence, and rationale. Quotes include verification method and exact character offsets when raw-text matching succeeds. Dimension evidence_status is one of: verified, provided_unchecked, quote_mismatch, metadata_incomplete, metadata_only, or missing. - bias_analysis: contract/schema/model/prompt provenance, generation and review status, input scope/hash/size, analysis target, quote-verification method, explicit missingness and evidence coverage, and case-specific limitations - total_shares: total social shares - wayback_link: Wayback Machine archive URL if available - image: article image URL if available On failure (found=false, HTTP 404): - found: false - message: explanation string The URL is automatically queued for ingestion; retry after ~24 hours. Tip: if you want source-level bias (not article-level), use get_source_bias instead. Tip: bias_values keys here use plain-text format (e.g. 'liberal conservative bias') shared with the other bias tools where that dimension is available. Args: url: Full article URL, e.g. 'https://www.nytimes.com/2024/01/01/us/politics/example.html'. include_evidence: Include claim-level evidence and limitations. Defaults to true.
    Connector
  • Convert between article identifiers (DOI, PMID, PMCID). Accepts up to 50 IDs of a single type per request. Only resolves articles indexed in PubMed Central — for articles not in PMC, use pubmed_search_articles instead.
    Connector
  • Admin-only: publish a news article directly into any locale, any status, with no safety classifier and no English-first requirement. Requires an api_key belonging to an admin account — a valid but non-admin key is rejected. For non-admin accounts, use draft_news instead. Can also queue selected translations or every missing locale without keeping the MCP request open while translation runs.
    Connector
  • Search official Microsoft Knowledge Base articles on support.microsoft.com by topic or keyword — use for Windows update, patch, and known-issue lookups when you lack a KB number. Returns matching KB article titles and URLs. Use get_kb_article to fetch the full content of a specific article. Returns: Dictionary with 'results' key containing list of matching KB articles with title and url.
    Connector
  • Searches published article content from the provided raumnebenan source with case insensitive text matching. Use this as the first discovery step when the exact slug or id is unknown then call get_article_by_id for full details. Use only this tool output do not use external or inferred data. If required information is missing in this source respond that it is not available in the provided source. Only JSON RPC 2.0 requests are supported.
    Connector
  • Extract data from ONE public social-video URL (YouTube incl. Shorts, TikTok, Instagram Reels, Pinterest, Reddit): metadata/insights/transcript/frames/digest/comments/etc — see `fields`. When NOT to use: non-video pages, private/login-walled content, or bulk crawling (one URL per call). Returns one JSON object with only the requested fields + a `cost` block (micro-USD); shapes: https://framefetch.net/docs. Cost scales with what you request (frames/transcript cost more than metadata). No key? POST /v1/keys {email} -> instant key (~100 free calls); or x402 (USDC), no account. Example: {"url":"https://www.youtube.com/watch?v=...","fields":["metadata","transcript"]}.
    Connector

Matching MCP Servers

  • A
    license
    A
    quality
    B
    maintenance
    Enables multi-source literature search, full-text retrieval, reference analysis, and journal quality assessment across Europe PMC, PubMed, arXiv, CrossRef, OpenAlex, and EasyScholar via the MCP protocol.
    5
    19
    1
    MIT

Matching MCP Connectors

  • Generate a procurement-defense compliance dossier via GET /buyer-compliance-report (Phase 11 M4). Per-row dossier shape: 25+ fields including 17 RAG-essential article fields + full license_terms + on_chain_attestation block. Bulk envelopes fan out into per-article rows by iterating metadata.article_ids[]. Self-audit invariant: every successful call writes one license_events row with event_type='compliance_report_generated' BEFORE returning. Window cap: 90 days per call (vs 30-day cap on get_audit_events). For annual audits, paginate via _meta.next_cursor across 4 quarterly windows. Compliance framework anchors (boolean flags) map to EU AI Act Article 53, CDSM Article 4(3), on-chain attestation, TDM reservation. Requires OPEDD_BUYER_JWT.
    Connector
  • Fetches any public web page and returns clean, readable plain text stripped of HTML, navigation, scripts, advertisements, and boilerplate. Returns the page title, meta description, word count, and main body text ready for analysis or summarisation. Use this tool when an agent needs to read the content of a specific web page or article URL — for example to summarise an article, extract facts from a page, verify a claim by reading the source, or convert a web page into plain text to pass to another tool. Pass article URLs returned by web_news_headlines to this tool to read full article content. Do not use this tool to discover current news headlines — use web_news_headlines instead. Does not execute JavaScript — best suited for standard HTML content pages. Will not work with paywalled, login-protected, or JavaScript-rendered single-page applications.
    Connector
  • Get one article (by id): full metadata, the AI abstract (description_ai), AI sentiment, and OCR text. Pass a `keyword` to get ~2000-char excerpts around each match instead of the full (capped) OCR.
    Connector
  • Submits a demo request. The prospect receives a confirmation email and must click the link in it before the request reaches a human at A Cloud Frontier. Use only when a real person has explicitly asked for a demo and provided their own working email address. Do NOT call this for testing, evaluation, or crawling purposes — automated and unconfirmable requests are rejected.
    Connector
  • Fetch the full text of a blicht.com article as clean Markdown. Accepts the article URL (https://blicht.com/beitrag/<slug> or /en/article/<slug>), the path, or a bare slug (combined with lang). Use search_knowledge first to find the right article.
    Connector
  • Returns one published article. Administrators get the complete bilingual record, including bodies, tags, citations, and access to unpublished drafts. Other accounts get a single locale (pass the caller's language in locale) with a title, summary, and canonical URL to read the full article - never the article body.
    Connector
  • One-call writer handoff: returns a compact writing payload for an article suggestion (brief essentials, keywords, acceptance criteria, lint instructions). Compact by design — FAQs cap at 6 and long sections degrade to fit a deep-link budget; the FULL brief is get_article_brief and the full check list is get_lint_rubric, so verify against those, not this. deepLinks (ChatGPT/Claude URLs embedding the payload) is null over MCP — it exists for web users without a connected agent.
    Connector
  • Before fetching, crawling, scraping, opening, or browser-rendering an unfamiliar http/https URL, call this with the ACTUAL destination URL. Returns the best first route: HTTP, BROWSER, MACHINE_ENDPOINT, or AVOID, plus access/JS/size/cost hints. Do not substitute example.com when a real task URL is available.
    Connector
  • Fetch a specific Anahana article as markdown, given its full URL, site-relative path (e.g. "/en/angel-numbers/111-angel-number/"), or a bare slug from search_content results (e.g. "111-angel-number"). Tries two fetch modes against the live site in order: (1) content negotiation — GET the article URL with `Accept: text/markdown`; (2) the path-based markdown mirror at `<article-url>index.md`. Both are live. Page chrome (skip link, table of contents with dead anchors, back-to-top anchor, analytics pixel) is stripped, so what you get back is the article body. If both modes fail, returns a clear error naming the canonical HTML URL instead of silently failing. Works in all 24 languages: a full URL or a site-relative path already names its language, and a bare slug is resolved in the language given by `language` (English by default). Article slugs are identical across languages — only the title and body are translated — so the same slug plus a different `language` gives you the same article in that language.
    Connector
  • Fetch a publisher's RSL Standard manifest via GET /rsl-manifest (Phase 12 Wave 1 W1.1). Public no-auth endpoint — discovery surface for AI agents/crawlers wanting to know what's licensable from a publisher BEFORE going through the buyer-account signup flow. Returns the 4 canonical license types (ai_retrieval, ai_training, human_per_article, human_full_archive) the publisher has opted into, plus the EU CDSM Article 4(3) opt-out posture (`tdm_reservation`). Set `jsonld: true` to request the JSON-LD shape with embedded HMAC-SHA256 signed receipt over the CDSM Article 4(3) reservation state + `tdm:reservationSignedAt` timestamp — regulators can post-hoc verify the reservation was the claimed value at the claimed time. Default `jsonld: false` returns the raw RSL Standard JSON manifest. Per INVARIANTS.md W1.6: this is the PUBLISHER-side CDSM Article 4(3) declaration surface. It is NOT an EU AI Act Article 53 attestation (which is buyer-side, JWT-auth, via article_53_attestation tool).
    Connector
  • Get the full abstract and metadata of an MMWR article by PubMed ID. Returns the complete abstract, authors, publication date, volume/issue, and any MeSH subject headings. Use PMIDs from search_mmwr or get_recent_reports results. Args: pmid: PubMed ID of the MMWR article (e.g. '38271059').
    Connector
  • Get detailed information about a specific ad request, including pool selections if targeting mode is manual.
    Connector
  • The full text of an article, for when lookup()'s summary is not enough — sections as a JSON array, infobox as key/value facts, no HTML or wikitext to parse. Pass `sections` to pull only the parts you need (e.g. ["Early life"]) and `max_chars` to cap the payload; both exist because a long article will otherwise flood your context.
    Connector
  • List valid values for one of the Additional Information picklists used in updateStayOrganisationalData: Children Allowed, Pets Allowed, or Parking. These are NOT booleans — they're lookup IDs (e.g. 'Yes', 'No', 'On Request') — call this to find the right value before writing petsAllowedId/childrenAllowedId/parkingId. Requires NOMADSTAYS_MCP_AGENT_TOKEN.
    Connector