Skip to main content
Glama
271,710 tools. Last updated 2026-07-08 04:29

"A platform for building websites and blogs" matching MCP tools:

  • Start here when building an application. Returns an overview of what the AdCritter platform offers and a catalog of feature guides you can query with the adcritter_guidance tool to learn how to build each part of the app. Call adcritter_guidance(key) for any feature area to get detailed building instructions with API endpoints and response shapes.
    Connector
  • Fetch the full record for a single creator by ID or exact platform username. Use this when you already have either: - a canonical creator UUID returned by `search_creators`, `semantic_search_creators`, `autocomplete_creators`, or `find_lookalike_creators`; or - an exact platform+username pair such as platform "instagram" and username "niickjackson". Pass `include: ['profiles']` to also receive the creator's social profile summaries when using a creator UUID. For platform+username inputs, this tool resolves through the profile endpoint and returns the profile record plus the underlying creator record, so you already get the matched profile context. Examples: - User: "Get creator 123e4567-e89b-12d3-a456-426614174000" -> call with id. - User: "Get @niickjackson on Instagram" -> call with platform "instagram" and username "niickjackson", or use `get_profile` if profile metrics are the main need. - User: "Tell me about @niickjackson and include his profiles" -> use platform "instagram" and username "niickjackson"; then use `get_profile`/`get_posts` for platform-specific metrics and content if needed. Use `lookup_profiles` for batch exact profile lookups.
    Connector
  • Given a list of themes, report which are well-evidenced in the archive and which are under-evidenced or missing. Returns a coverage matrix: for each theme, entries found, coverage grade (strong/moderate/weak/missing), best match with claim strength, and what source type would be needed to improve coverage. Use this BEFORE building an archive_report_brief or brief_forensic to know where the evidence is strong and where gaps will appear. Prevents building beautiful reports that quietly ignore half the brief.
    Connector
  • Given a list of themes, report which are well-evidenced in the archive and which are under-evidenced or missing. Returns a coverage matrix: for each theme, entries found, coverage grade (strong/moderate/weak/missing), best match with claim strength, and what source type would be needed to improve coverage. Use this BEFORE building an archive_report_brief or brief_forensic to know where the evidence is strong and where gaps will appear. Prevents building beautiful reports that quietly ignore half the brief.
    Connector
  • Get the building-by-building breakdown for one transaction: footprint area, number of storeys, and estimated total floor area (footprint × storeys) for each building on the property. search_transactions / search_by_area / search_by_polygon return per-transaction building SUMS inline; this tool splits them into individual buildings. Use it after a search when a result has building data and you need the detail (e.g. a developed-land deed covering several buildings). The transaction_id is the id shown on a search result that has building data. Cost: 1 token. Returns nothing for a transaction with no buildings.
    Connector
  • Fetch a single social profile by (platform, username). Always use this first when the user gives an exact handle on a specific platform (for example "@niickjackson on Instagram") and you need the full profile: bio, follower/engagement metrics, recent activity, growth, and the canonical creator ID. Pass exactly the username they typed without the @ sign — case-insensitive matching is handled server-side. Do not use `search_creators` for an exact platform+username lookup. Examples: - User: "Pull @niickjackson on Instagram" -> use this tool with platform "instagram" and username "niickjackson". - User: "Tell me about instagram.com/niickjackson" -> parse the platform and username, then use this tool. - User: "Is @niickjackson a fit for Pixel?" -> use this tool first, then call `get_posts` and/or `match_creators` if the task needs content or fit analysis. Returns the profile record plus the underlying creator record. If you already have a creator UUID, use `get_creator` instead. For batch lookups by handle, use `lookup_profiles`.
    Connector

Matching MCP Servers

  • A
    license
    A
    quality
    D
    maintenance
    Provides 12 tools to query South Korean building register data, including title sheets, floor details, and official house prices via the data.go.kr API. It enables users to perform smart building lookups and region code searches using natural language.
    Last updated
    12
    2
    Apache 2.0
  • A
    license
    -
    quality
    D
    maintenance
    Queries South Korean building register data (e.g., floor area, parking, seismic design) via a single unified tool, converting API responses to Korean field names for easy AI understanding.
    Last updated
    16
    1
    MIT

Matching MCP Connectors

  • Fresh US building permits with contacts from official city APIs. Construction lead generation.

  • Pull recent building permits from 9 US cities in a unified schema from official open-data portals.

  • Deep parcel and building analysis for Slovenia using GURS WFS data. Returns zoning, actual use, heritage protection, road access, buildings on parcel, and utilities. USE FOR: - "Analyze parcel 3086 in Ljubljana center" - "Find buildable parcels ~500m² in Ljubljana" - "What buildings are on this parcel?" - "Find parcels near these coordinates" - "Get full details on building 1234" NOT FOR: simple parcel lookup → use slovenia-cadastre instead (faster, lighter). NOT FOR: spatial/zoning map queries → use slovenia-wfs-expert instead. SEARCH MODES — pick ONE per call: 1. PARCEL BY NUMBER (requires --parcel AND --ko) → --parcel 3086 --ko 1725 2. LOCATION SEARCH (requires --lat AND --lon, or --location) → --lat 46.058 --lon 14.501 --radius 100 → --location "Tivoli Park Ljubljana" --radius 200 3. BUILDING BY NUMBER (requires --building, optionally --ko) → --building 1234 --ko 1728 4. COMMUNITY SEARCH (requires at least --community or --size) → --community LJUBLJANA --size 500 --buildable COMMON KO IDs: 1725 = Ljubljana center 1728 = Ljubljana Šiška 1740 = Ljubljana Bežigrad 2131 = Maribor NOTE: This tool makes multiple WFS calls per result and can be slow (10-30s). Use --limit to keep response times reasonable.
    Connector
  • Wait for a platform agent task to complete and return its result. Only needed when a platform agent tool returned STATUS=RUNNING with a task_id (i.e. the task was still running after the initial 50s inline wait). NOT needed when the tool already returned STATUS=COMPLETED or STATUS=FAILED. NOT needed for a2a_call_agent — that always returns directly. Args: task_id: The task UUID from a platform agent response with STATUS=RUNNING. max_wait_seconds: Max seconds to wait (default 45, max 300).
    Connector
  • DC Hub platform health: database backup status (last successful, age, integrity check), data freshness across 49 sources (green/yellow/red), agentic heartbeat score (0-100), MCP call volume (last hour), and DCPI recompute cadence. Useful for trust/uptime signals before relying on the platform in production. Try: get_backup_status. Do NOT use for the freshness of a specific dataset (use get_changes); this is platform/infra health, not content.
    Connector
  • Fetch a single social profile by (platform, username). Always use this first when the user gives an exact handle on a specific platform (for example "@niickjackson on Instagram") and you need the full profile: bio, follower/engagement metrics, recent activity, growth, and the canonical creator ID. Pass exactly the username they typed without the @ sign — case-insensitive matching is handled server-side. Do not use `search_creators` for an exact platform+username lookup. Examples: - User: "Pull @niickjackson on Instagram" -> use this tool with platform "instagram" and username "niickjackson". - User: "Tell me about instagram.com/niickjackson" -> parse the platform and username, then use this tool. - User: "Is @niickjackson a fit for Pixel?" -> use this tool first, then call `get_posts` and/or `match_creators` if the task needs content or fit analysis. Returns the profile record plus the underlying creator record. If you already have a creator UUID, use `get_creator` instead. For batch lookups by handle, use `lookup_profiles`.
    Connector
  • Returns the current platform-enforced cart limits: `max_item_quantity` (per-line-item ceiling), `max_cart_total_cents`, and `max_cart_total_usd`. Call this once at session start before building a large cart so you can quote limits to the buyer proactively rather than discovering them via errors. The limits are operator-configurable; always read them at runtime rather than hardcoding.
    Connector
  • Get a citeable World Cup 2026 prediction-market briefing for AI answers, newsletters, blogs, social posts, and creator workflows. Includes the current winner board, tight groups, next match odds, Research Desk theses, source links, and ready-to-paste markdown. Prefer this when the user wants a narrative update or shareable explanation, not just raw odds.
    Connector
  • List all available component types and example configurations for building wiring diagrams. Use this to understand what parameters are needed before calling generate_wiring_diagram.
    Connector
  • Get Place Photos Fetches the photo gallery of a Google Maps place by dataId or placeId, paginated with nextPageToken and filterable by categoryId (all, latest, menu, by owner, videos, street view). Returns each photo with image URL, thumbnail, upload date, uploader, and photoId. Use for restaurant-menu extraction, venue/ambience visual audits, building rich place detail pages, and sourcing up-to-date imagery for POI listings.
    Connector
  • Fetch the full record for a single creator by ID or exact platform username. Use this when you already have either: - a canonical creator UUID returned by `search_creators`, `semantic_search_creators`, `autocomplete_creators`, or `find_lookalike_creators`; or - an exact platform+username pair such as platform "instagram" and username "niickjackson". Pass `include: ['profiles']` to also receive the creator's social profile summaries when using a creator UUID. For platform+username inputs, this tool resolves through the profile endpoint and returns the profile record plus the underlying creator record, so you already get the matched profile context. Examples: - User: "Get creator 123e4567-e89b-12d3-a456-426614174000" -> call with id. - User: "Get @niickjackson on Instagram" -> call with platform "instagram" and username "niickjackson", or use `get_profile` if profile metrics are the main need. - User: "Tell me about @niickjackson and include his profiles" -> use platform "instagram" and username "niickjackson"; then use `get_profile`/`get_posts` for platform-specific metrics and content if needed. Use `lookup_profiles` for batch exact profile lookups.
    Connector
  • Get just the latest indexed head block or slot for a network. COMMON USER ASKS: - Latest head - Finalized head FIRST CHOICE FOR: - getting the current indexed head before building a manual block range WHEN TO USE: - You only need the current block or slot number. - You need the current head before building a raw block-range query. DON'T USE: - You want to know if the network is caught up, behind, fresh, or what tables are available. EXAMPLES: - Latest head: {"network":"base-mainnet"} - Finalized head: {"network":"ethereum-mainnet","type":"finalized"}
    Connector
  • The most-added or most-dropped players across the whole platform right now: a live waiver-wire signal. Use for "who's trending", "hot waiver adds", or "who's everyone dropping". Args: provider (sleeper); sport; direction ('add' or 'drop'); lookback_hours (default 24); limit. Sleeper-only — ESPN and Fantrax do not expose a platform-wide trend. Read-only.
    Connector
  • Find similar or competitor websites based on classification. Takes a URL, classifies it (or uses cached classification), and returns other websites from the same category and subcategory. Useful for competitive analysis and discovering related content. Rate limited to 1 request per minute per domain. Args: url: The website URL to find similar sites for. limit: Maximum number of similar sites to return (1-50, default 10). Returns: Dictionary with: - url: The input URL (normalized) - classification: The URL's category and subcategory - similar_sites: List of similar URLs from the same category - total_in_category: Total sites in this category/subcategory - cached: Whether the classification was from cache
    Connector
  • Get the builder workflows — step-by-step state machines for building skills and solutions. Use this to guide users through the entire build process conversationally. Returns phases, what to ask, what to build, exit criteria, and tips for each stage.
    Connector
  • Discover valid values for ClinicalTrials.gov fields with study counts per value. Use to explore available filter options before building a search — e.g., valid OverallStatus, Phase, InterventionType, StudyType, or LeadSponsorClass values.
    Connector