Skip to main content
Glama
729,153 tools. Updated 2026-10-31 17:19

"A guide to writing for publication" matching MCP tools:

  • What to know before going to a venue, from UPFRONT's venue guide: the bag policy and what fans can bring, gates and entry, parking, getting there by transit or rideshare, and food and drink, including what the guide says about gluten-free, vegetarian or vegan, halal and kosher food. Matches questions like "what's the bag policy at MetLife?", "when do doors open at MSG?" or "where do I park for Lambeau?". venue: the venue's name ("MetLife Stadium", "MSG", "Lumen Field, Seattle"). topics: optional; only these parts, at more length: any of "bags", "entry", "parking", "transit", "food". Without it, every part. Covers the 36 stadiums, arenas and amphitheaters UPFRONT has a guide for; for any other venue the answer says so and lists the ones with guides. Each part is the guide's own words ("text", plus the guide's "faq" questions and answers). factsLastChecked is the date UPFRONT last checked the guide's facts; rules can change for a single event, and the venue's own event page has the final word. guideUrl is the guide on UPFRONT. dietary lists what the guide says per diet; dietaryNotMentioned lists diets the guide doesn't cover, which doesn't mean the venue has nothing for them.
    ConnectorNo auth
  • Create new guides Create one or more new guides based on provided queries. Each guide targets exactly ONE engine and ONE analysis mode, chosen with the optional `source` field (default `google`). How to request each guide type: 1. Google SERP guide (1 credit per guide): omit `source`, or pass `source: "google"`. Example payload: {"queries": ["best crm"], "lang": "en-us"} 1bis. Google AI Overview guide (1 credit per guide). Two modes, like AI engines: `source: "google_ai_overview"` builds the guide from the TEXT of Google's AI answers (AI Overview, completed with AI Mode answers) ; `source: "google_ai_overview_citations"` builds it from the content of the web SOURCES those answers cite (recommended for GEO). Same language/country parameters as a Google SERP guide, 1 credit per guide in both modes. Example payload: {"queries": ["best crm"], "lang": "en-us", "source": "google_ai_overview_citations"} 2. LLM ANSWER guide (4 credits per guide): pass the engine name alone, e.g. `source: "chatgpt"`. The guide is built from the answer text the AI generates for the query. Example payload: {"queries": ["best crm"], "lang": "en-us", "source": "chatgpt"} 3. LLM CITATIONS guide (4 credits per guide) [RECOMMENDED AI mode]: pass the engine name with the `_citations` suffix, e.g. `source: "chatgpt_citations"`. The guide is built from the content of the web pages the AI cites in its answer. Example payload: {"queries": ["best crm"], "lang": "en-us", "source": "chatgpt_citations"} Which AI mode to pick? For GEO (getting a page visible in AI answers), prefer `<engine>_citations`: AI engines send traffic by CITING pages as sources, so the winning move is to look like the pages they cite. The answer-text mode (`<engine>` alone) is mostly useful to analyze how the AI phrases its own answer. When in doubt, pick `<engine>_citations`. The same two modes exist for every AI engine (chatgpt, perplexity, claude, gemini, grok, mistral, deepseek). To optimize the same page for several engines or modes (e.g. Google AND ChatGPT answers AND ChatGPT sources), create one guide per source value on the same query. IMPORTANT, HOW TO READ THE RESPONSE OF THIS ENDPOINT, WHICH SPENDS CREDITS. Queries listed in `guidesFailed` are PROVEN not to have produced a guide and their credit was given back (unless the account has unlimited credits, where nothing was reserved): re-sending them is free and correct. Queries listed in `guidesUnknown` have an UNDECIDABLE outcome and their credit is deliberately KEPT, because the guide was most likely written: DO NOT re-send them, you would pay for the same guide twice. Look them up in `GET /api/v1/guides` after a few minutes instead, and contact support if nothing shows up. Finally, a `200` is NOT a promise that every query produced a guide: compare `guides.length` with the number of queries you sent, never read `success` alone, and never re-send a query just because it is missing from `guides`.
    ConnectorNo auth
  • <summary>Replace the user's writing style guide for one channel, the voice Sliq writes in there. A set guide overrides the communication style in memory, so when the user wants to sound different in a channel that has a guide, change the guide. It replaces text the user wrote or approved: keep everything they didn't ask to change, and tell them what you changed. To edit a guide, read it with get_writing_style_guide and pass back the whole new guide, without the notes that tool appends after it. The other channels keep their guides.</summary> <returns> <description>The writing style settings after the change.</description> </returns>
    ConnectorOAuth
  • Returns an official GuruWalk support guide for a specific traveler-support topic. GuruWalk is a platform for free walking tours and paid activities; these guides are GuruWalk's own source of truth on how bookings, cancellations, account settings and contacting guides actually work, including current policies and the exact URLs travelers should use. These guides apply only to bookings and accounts on guruwalk.com. Available topics: - account_settings: The traveler wants to manage their GuruWalk account: edit their details (name, surname, phone, city, password), change their email, stop receiving emails / unsubscribe, or delete their account; or they can't access their account. These are concrete steps you shouldn't improvise: consult this before answering. - contact_guru: The traveler wants to contact or coordinate something with the guide of their GuruWalk booking, or thinks they are talking directly to the guide: they can't find them at the meeting point, the guide didn't show up, they're running late, they treat you as if you were the guide, ask for the tour photos, or ask about bringing a pet or paying the guide, or have a question only the guide can answer. - free_tour_modification: The traveler wants to modify or reschedule their GuruWalk free tour — change the day, time, language or number of people — or asks how to do it. - group_booking: The traveler wants to book or extend a GuruWalk booking for a group (they usually say how many; treat it as a large group from around 6 people), asks how to book for many people, can't book for the whole group, sees a large-group notice or is asked for a card or payment for the group, or had a booking cancelled as "group or duplicate". The rules aren't intuitive; consult this before advising. - paid_cancellation: The traveler wants to cancel or change a paid activity booked on GuruWalk, asks about a refund, or can't cancel from their account. Call this when the traveler raises a support topic covered above. Pass the exact topic; the guide content is returned.
    ConnectorNo auth
  • Mamanida's editorial buying guides for one storefront, in that storefront's own language. Called without `guide` it lists the published guides (metadata only: title, deck, meta description, pillar, topics, dates and the canonical Mamanida URL), optionally filtered by `topic`. Called with `guide` (the guide slug from the listing) it returns that one localized edition plus its structured body: paragraphs, headings, lists, comparison tables, callouts, links to other guides and category calls-to-action. A `category_cta` gives a `category_slug` you can pass straight to search_products, which is the intended guide → category → product path. Retailer and affiliate URLs are never returned.
    ConnectorNo auth
  • Read the full text of a cooking guide from recipes-daily.com, as markdown. Call this when search_recipes lists a guide that answers the question — how or why something works in the kitchen, how to store or substitute an ingredient, how to use a piece of equipment — and answer from what it says rather than from memory, citing its URL. Pass the guide URL exactly as search_recipes returned it. For recipes, use show_recipes instead: a recipe is a page the person cooks from, not text to retell.
    ConnectorNo auth

Matching MCP Servers

  • A
    license
    Not graded
    quality
    C
    maintenance
    An MCP service for AI-assisted reasoning and editing on long-form fiction projects. It builds a structured index from scene files for targeted context retrieval.
    218 npm
    1
    AGPL 3.0
  • A
    license
    Not graded
    quality
    C
    maintenance
    Keylessly retrieves as-published European patent documents from the EPO's European Publication Server — publication dates, per-date listings of issued EP publications with kind codes, titles and applicants, and full text (bibliographic data, abstract, claims, description) for granted patents and directly-filed applications. It also flags cases where only bibliographic records exist, such as PCT-route applications whose specifications were published by WIPO instead.
    70 npm
    MIT

Matching MCP Connectors

  • Read the Bridge integration guide for a topic — the supported, opinionated way to consume Bridge from application code. Call this BEFORE writing or changing app code that reads a feature flag, renders billing or team UI, or wires authentication, and before hand-rolling anything against the SDK: the SDKs ship declarative surfaces for these cases (components, route guards, decorators) and reimplementing them against SDK internals is the most common integration mistake. Per-framework topics (framework REQUIRED): integration (first-time setup) | auth | feature-flags | billing | team | branding. Framework-agnostic MASTER topics (framework is IGNORED — omit it): master, the end-to-end auth integration prompt served by `bridge guide`, which orchestrates project discovery and then routes to the per-framework guides; flags-master and billing-master, the same orchestration for a flags-only or billing-only integration; mechanisms, how limits, upgrades and customization work; orientation, what Bridge does (the same map get_started returns); fit-together, how roles, plans, limits and flags fit together; integration-success, the message to show the developer when an integration is done. Before setting up flags, roles, plans or limits, read topic=fit-together. Start at topic=master when integrating Bridge into a project for the first time. framework: svelte | react | angular | nextjs | nestjs | express — pass the one the target app actually uses; this server cannot detect it. Returns the guide as markdown plus its source URL. Guidance is a default, not a mandate — follow the user's stated preference when it differs.
    ConnectorOAuth
  • Read the Signals Quick Reference guide when the user asks for that guide or its documented entries. This is the document-reading shortcut for kb_get_document slug=10-signals-quick-reference, not an additional validation step. Use view=overview for its outline or view=section with a known anchor for a passage. Content defaults to 6000 characters; offset and next_offset count characters within the selected body. Continue only for requested missing text. Reserve full=True for explicit downloads. For conceptual signal combinations use query_knowledge op=ask. For executable signal names and parameters needed to construct a strategy use the runtime catalogue, not this educational guide.
    ConnectorNo auth
  • Return the guide to writing a Kadal Deck: how to shape a talk (one idea per slide, clicks, speaker notes, layouts, live audience components), the layouts and components at a glance, then the full MDX and click syntax. Use it once before drafting or editing a deck.mdx; use deck_reference instead to look up one component, layout or option in detail. Read-only, no arguments; the answer is long markdown, so fetch it once per session rather than per slide.
    ConnectorOAuth
  • Export citations for 1–25 VHP IDs or URLs. format is text or ris; target is publication (the cataloged work) or page (the VHP web page). Missing publication metadata returns a per-item error; choose page to cite a biography or history page.
    ConnectorNo auth
  • Save a guide on a project. With guide_id it is a new version of that guide; with a name no main guide on the project has yet it starts a new guide (one project can hold many videos); otherwise it is a new version of the newest guide. kind "auth" is the login flow (never recorded, may use {USERNAME}/{PASSWORD}); kind "main" is the walkthrough that becomes the video. Call get_guide_instructions before writing a guide and validate_guide before saving it.
    ConnectorOAuth
  • Read Fieldproxy's app-building reference. topic='index' lists every guide and widget. Guides: 'app' (app JSON), 'view' (screen JSON), 'actions' (onclick/onchange/navigation), 'schema' and 'tenant-schema' (data tables), 'theming', 'design', 'dashboards', and more. Any widget type name (e.g. 'table', 'form', 'map_widget') returns that widget's full syntax. Read the relevant doc before writing any app or screen JSON — it is more reliable than memory. Web and mobile apps have DIFFERENT references: pass platform 'mobile' for a mobile app (no `type: "web"`).
    ConnectorAPI key
  • Fetch an xTiles guide/documentation document by its `xtiles://guide/...` URI. The same documents are also exposed as MCP resources — use this tool when your client cannot read resources directly. Before generating Markdown for any `*_from_markdown` tool, read `xtiles://guide/markdown/overview` (and `/canvas`, `/collections`, `/blocks`) to get the syntax. `xtiles://guide/markdown/design` holds the colours, styles, layout and tab colours created content takes. `xtiles://guide/markdown/tasks` covers tasks — where a task goes, whose it is, and which dates to set.
    ConnectorOAuth
  • Browse Fly Frugal's published day-by-day budget travel itineraries. Use this to discover which destinations have a guide, then call get_itinerary with a returned slug for one guide's preview. Each item has slug, country_name, tagline, days_count, a preview, cover and first-day image URLs, price_cents and currency for the full guide, updated_at, and pdf_ready. Results are newest first. Only public previews are returned; the paid full guide is never included.
    ConnectorNo auth
  • Return Genpio's guide for one country or market: what that market's platforms allow for an AI livestream host, quoted from their own policies with links, which local platforms Genpio does not stream to, which languages Genpio Voices speaks there, and the guide's full text as Markdown. Use it whenever a question names a country, and pass the language the person is writing in so the guide comes back in it. For a country without a guide it says so and gives only what holds worldwide; do not carry another country's platform rules over to it. With no country, it lists every guide.
    ConnectorNo auth
  • Returns the drafting guide for one channel: the honesty rules every draft follows, the channel's craft, general writing craft (plus AEO/GEO writing on blog, faq and competitor_page, and a visual brief on instagram, tiktok, youtube and pinterest: shot list, on-screen text, thumbnail and script), when a post needs media and where to find it, design craft for a new graphic, this workspace's brand voice and its colors and fonts, content exclusions and notes for the channel, and the platform limits. Check a draft against it before saving, then pass its guideVersion to save_post. Claims and sources are not in the guide: call get_brand_context for those. Does not change anything. Related: save_post, get_brand_context, get_channel_rules.
    ConnectorOAuth
  • Discover checked Florida or California launch/trailer and beach parking guides. Supply state, optionally an exact guide ID; omit id to list available guides and IDs. Returns official sources, checkedAt (research date, not publication time), entrance directions when researched, permit/fee/access guidance, construction notices and published capacity where supplied. Coverage is selected locations, not every launch. Unknown IDs return no guide. availability is always null: no live occupancy, opening or reopening feed is connected. Never substitute ordinary car-lot parking for trailer permission. Facility inventory is available through get_poi_details for supported Florida POI IDs. Units: ft, kt, s, F, mi; directions FROM. Returns data and source/freshness metadata.
    ConnectorNo auth
  • Everything needed to write the post for one plan item, or to refresh a published one: the keyword with its volume and difficulty, the live Google top 10 with the word count and H2s of the strongest articles, Google's AI answer and the sites it cites, People Also Ask, related searches, what Rillow remembers about the site, the site's own pages to link to and a writing guide. For a published post, or with refresh: true, it adds the post's rank history and the site's Search Console queries from the last 28 days that contain the keyword (site-wide, not per page). Call it before writing. Google results are cached on the plan item for 7 days, so calling it again that week is free.
    ConnectorOAuth
  • How to do one kind of SEO work well, written for you, with the rules for every guide at the end. Read the matching guide before you start that work: new-site (a site new to search or about to launch), audit (review or fix an existing site, or a traffic drop), technical (indexing, canonicals, redirects, sitemaps, rendering, speed), keywords (picking topics and planning pages), content (writing or refreshing posts and product pages), links (internal links and backlinks), ai-search (ChatGPT, Perplexity, AI Overviews), agents (making the site usable by AI agents), measure (judging a change, picking posts to refresh), writing (how every text you write for the site should read: posts, pages, titles, descriptions, emails; read it before writing anything but a post, whose get_brief includes it). get_project names the guide that fits the site. Free, it uses no credits.
    ConnectorOAuth
  • Searches Google Scholar and returns up to 20 publications (title, url, publication, snippet, cited_by, cites_id), optionally limited to a range of publication years. Use it for academic papers and citation counts. It does not return full texts, is not for patents (use search_patents) and is not general web search (use google_search). A search with no matches is charged; errors are not. Required: query.
    ConnectorNo auth
  • Look up what a deck can use — components with props, defaults and examples, layouts, backgrounds, themes, frontmatter keys, CLI commands — from the engine's own catalog (exact for @kadal/deck 0.11.0), plus the docs' guides. Use it to check a component or option before writing it; use authoring_guide instead for the overall how-to. Read-only. Pass one mode: nothing for an index of sections and guides, `section` (plus `name` for one entry), `topic` for a guide in full, or `search` for the best matches across both; if several are given, `section` wins, then `topic`. An unknown section, entry or topic is an error that lists the valid ones.
    ConnectorOAuth