"Information about playwrights and theatrical writing" matching MCP tools:

• update_password_policyA

  The BridgeA

  Set the session token lifetimes on the Bridge app: accessTokenTTL and refreshTokenTTL, both in SECONDS. Only the fields you pass are changed. IMPORTANT — despite the name (kept for parity with `bridge auth password-policy`), this sets token TTLs and NOTHING about passwords: Bridge exposes no password-complexity, rotation or reuse policy on the management API, so if the user asked for password rules, say so instead of calling this. The access token TTL controls how often a client silently refreshes (short is safer, e.g. 900 = 15 minutes); the refresh token TTL controls how long a user stays logged in without re-authenticating (e.g. 2592000 = 30 days). Read the current values with get_auth_config. Before writing app code that consumes this, call get_integration_guide with topic=auth and the framework the app uses.

  ConnectorOAuth

• soclo_inbox_account_settings_saveA

  SocloC

  Separately change one connected account’s automatic-reply switch: pass its platform, accountId, enabled, the exact expectedUpdatedAt from soclo_inbox_settings (null only for an absent switch) and a stable UUID clientRequestId. Preview first; pass confirm: true only after owner approval. Needs manage:inbox. After an uncertain save, read soclo_inbox_settings and reconcile before writing again.

  Connector

  Destructive

  OAuth

• get_wedding_informationA

  The Hill KinabaluA

  Retrieve The Hill Kinabalu’s official public wedding venue and 2026/2027 package information, including capacity, event sizes, starting package prices, key inclusions, add-ons without prices, payment structures, and enquiry links. Use this when someone asks about weddings, wedding packages, the event venue, guest capacity, package pricing, or how to enquire. This tool does not check date availability or submit an enquiry.

  ConnectorNo auth

• cti_get_guidelinesA

  website-searchA

  Get Lenny Zeltser's expert CTI writing guidelines. Topics include tone, words, structure, executive_summary, voice, articles, summary, brief (one-page brief section guidance), handoffs (cross-server routing), methodology (the three subsections), fields (per-field guidance), and CTI-specific topics: attribution (full Six Signals prose), confidence (ICD-203 ladder), pyramid_of_pain, six_signals (signals table only), and anti_patterns. The general writing topics (tone/words/structure/executive_summary) now defer to `get_security_writing_guidelines` for the canonical Five Elements rules; CTI-specific content lives in the other topics. Pair the 'fields' topic with field_id for single-field guidance. This server never requests your campaign or threat-intel notes and instructs your AI to keep them local—templates and guidelines flow to your AI for local analysis.

  ConnectorNo auth

• update_load_test_notesA

  LoadsterA

  Replace the notes on a finished Load Test's Test Report — the only thing on a Load Test this surface edits. Ask the user before writing: notes belong to the user, and advising on a test never requires writing them. The text sent becomes the report's entire notes, so first read the current notes with get_load_test_report and preserve the user's content in what you send.

  Connector

  Destructive

  OAuth

• crypto_reportA

  EventTrader MCPB

  A short research report on what a link or a topic means for one coin, grounded in the coin's dashboard, with its own public page to share. To ask: pass symbol and about (a public http(s) link such as a post on X, a press release or an article, or a topic of 3 to 300 characters); the answer comes at once with status=writing and the report's id. To read: pass report_id (no key needed); status is writing, ready or unavailable. At most 6 reports an hour and one a minute. The report is written by EventTrader's AI and can be wrong. Asking needs a registered agent (API key). From EventTrader's crypto dashboards (cymetica.com/crypto). Every number carries its source and time; a number that failed a plausibility check is withheld, never guessed. Places no orders, moves no funds. Not financial advice.

  ConnectorNo auth

• xcut_find_outliersA

  XCut AI – Viral Content ResearchA

  Use this when the user asks which of a creator's, competitor's or their own posts performed best or beat the account's normal, or what works for an account before writing. Scores the latest 20, 30, 50 or 100 posts against that account's own median and says by how much each beat it. About 3-4 credits for 30 posts on Instagram or TikTok, none on YouTube, more on Facebook. Longer runs return a `job_id` for xcut_get_job. Do not use for a full metrics table (use xcut_profile_analytics) or for a topic across many accounts (use xcut_search_viral).

  ConnectorNo auth

• setThreadReplyingA

  NextmailB

  Tell the team you are writing a reply to an email thread, so getThreadTeam and the app show the others that you are replying and nobody answers twice. The mark lasts 30 seconds, so call it again while you are still writing, and with replying false once you have sent the reply or given up.

  Connector

  Destructive

  OAuth

• quick_checkA

  API Change FeedA

  Free. Before writing code against a library you may know only from older training data, check whether it changed since that version: verdict, major versions crossed, how many breaking changes, deprecations and security fixes, and the top three breaking headlines. Call upgrade_check (paid) for the full details with evidence.

  ConnectorNo auth

• quick_checkA

  API Change FeedA

  Free. Before writing code against a library you may know only from older training data, check whether it changed since that version: verdict, major versions crossed, how many breaking changes, deprecations and security fixes, and the top three breaking headlines. Call upgrade_check (paid) for the full details with evidence.

  ConnectorNo auth

• show_roomsA

  Roomza Hotel IntelligenceA

  REQUIRED whenever you present rooms. Whenever you are about to mention, recommend, or describe one or more specific rooms to the user, you MUST call this tool with those room UUIDs INSTEAD of writing the rooms in text. This is mandatory even when there is only ONE matching room — show it as a single hero card, never describe a lone room in prose. Call this BEFORE writing any prose about the rooms; the cards must appear first, then a brief summary. Pass room UUIDs (from get_hotel_rooms or search results) in ranked order, best first, 1 to 8 rooms. ALWAYS pass check_in and check_out when you know the user's dates: card prices are then for those exact dates. Without dates, cards show a typical from-price that can differ a lot from any specific dates. Each card shows photo, Roomza score, view, bed, and price. NEVER ask the user whether they want to see cards or images — just call this tool. When get_hotel_rooms returns no tracked rooms (a roomTypes list instead), call this with hotel_id and no room_ids: it renders the hotel's bookable room types as cards with photos and prices, each linking straight to booking.

  ConnectorNo auth

• graph_searchA

  Moltline RecallA

  Find what the graph knows about something, plus its neighbourhood. FREE. Scores entities by how many query words appear in the name, type and observations, then pulls in whatever is within the requested number of hops - because the useful answer to "what do we know about Acme" is usually Acme plus who it is connected to. Typical input {"graph": {...}, "query": "acme renewal", "hops": 1} returns {"matches": [{"name": "Acme Corp", "score": 3, "why": ["name", "observation"]}], "neighbourhood": {"entities": [...], "relations": [...]}, "hops": 1}. Use to read memory back before answering. Not for writing (graph_upsert) and not for narrowing by date, which graph_at_time does. Errors: on invalid, missing, or malformed input this tool never raises a protocol error; it returns {"error": "<what is wrong and how to fix it>"} (for example {"error": "query must contain at least one word or number"}). Every call is read-only and idempotent, so after correcting the input it is always safe to retry.

  ConnectorNo auth

• asksteps_get_formA

  askstepsA

  Reads one form of the connected asksteps account as a structure of steps and fields — the same shape asksteps_update_form takes. Requires "forms:read". ALWAYS call this before asksteps_update_form: the write replaces the whole form, so you need the current state to keep what you are not changing. The answer also tells you whether writing is allowed at all (field "editable").

  ConnectorNo auth

• list_fontsA

  MorphaReelsA

  List available font families across every source the editor knows about (Google + Bunny + Fontshare + Fontsource + Velvetyne) PLUS the project's user-uploaded custom_fonts (surfaced as source: "custom"). Use this to discover families before set_layer_text / add_text_layer when you don't know what to pick. Returns { fonts: [{family, source, weights, italics}], total, returned, sources }. Filter via `q` (case-insensitive substring on family), `source`, and/or `script` (only families that draw that writing system, e.g. "cyrillic", "arabic", "japanese": use it when the text is not in Latin letters); cap with `limit` (default 50, max 1000). Picking any returned family in font_family Just Works — the editor's loader dispatches to the right CSS/FontFace endpoint by source.

  ConnectorNo auth

• get_assetA

  Postclick by PPC.io: Landing Page CROA

  Free. Every design, page capture and logo has an asset_id on the field that holds it. Pass it here. Which form you ask for depends entirely on where the picture is going, and getting it wrong is expensive. `as: "url"` is the DEFAULT AND USUALLY RIGHT one: a public link, no login, full size. Use it for anything you publish with publish_page, and for showing somebody a design. `as: "bytes"` returns the picture itself, downscaled to about 1024 across so it fits in a conversation, and you embed it as data:<mime>;base64,<bytes>. Use it ONLY for a document you are writing in a place that refuses to load pictures from other websites, which includes artifacts. At full size one of these designs would be several hundred thousand tokens, so ask for bytes deliberately and not by habit.

  ConnectorNo auth

• save-prospect-draft-toolA

  CoderbudsA

  Internal Coderbuds staff only. Save an opener against a prospect for Elliot to read and send, and flag the row as waiting on him. **You cannot send anything.** Every message goes out under Elliot's name, from his own inbox or LinkedIn account, so the division is: you research, prioritise and write; he sends. This is where the writing goes. Write the message itself, not a description of one — no placeholders, no "[insert metric]". Ground every claim in what the worklist gave you and say plainly what is not verified. If you cannot write an honest opener because something is unconfirmed, do not invent it: use `update-prospect` to park the row with the question instead. Saving a draft flags the row, because a draft nobody is told about is a draft nobody sends. Recording the send later clears both.

  ConnectorOAuth

• update_athlete_profileA

  BlocksA

  Edit the athlete's profile — FTP (watts), running threshold pace, max/threshold HR, power/pace/HR zone boundaries, AND the about-you fields (birthdate, sex, heightCm, weightKg, weeklyHours, availableDays 0=Mon..6=Sun, experience). Every field is OPTIONAL: pass only what changes; everything else is preserved (safe partial update). Confirm new numbers with the athlete before writing (a changed FTP/weight moves every target). To set custom zones pass a sport's `zoneBounds` (5 strictly-ascending upper bounds) — that flips it to Manual; pass `autoZones:true` to revert. Same for `hrZoneBounds`/`autoHrZones`. Setting birthdate refreshes the age-based HRmax estimate unless maxHr was set manually — writing a sport's maxHr marks it manual, and autoMaxHr:true hands it back to the estimate. Server-validated; rejects an invalid edit instead of writing a broken profile. Only touches the profile, never the calendar or library. Read with get_athlete_profile first.

  Connector

  Destructive

  OAuth

• rewrite_scriptA

  Vixdeo — Tu Productor IAA

  Rewrites the WHOLE piece under the brief with the format's writer (the same revision pass the writing pipeline runs), then re-dresses only the scenes whose narration changed (visuals are kept). It covers a brief that spans the piece («more rhythm in the second act, and let the ending return to the thesis»); a single scene has its own re-authoring op. Asynchronous: returns a run id, and the project status reports the job by `run_id` — once `completed`, with the new version id (`job.result.editorialVersionId`, also in `latestRunByKind.editorial_rewrite`). `as_branch=false` (default) makes the result THE CUT the line renders, as committing a draft does. Writers that require spend confirmation need `confirm_spend=true`. Requires `write`. Spends LLM budget: a full script pass, priced like the writing profile of the piece (`writingProfiles[].measure` in the catalogue of formats).

  Connector

  Destructive

  API key

• list_hook_rulesA

  KreatorMeshA

  List the rules KreatorMesh has learned about what works for each account, from hook tests run on its real audience rather than generic advice. Each rule has its text, the account and platform it applies to, the measured effect (effectRatio: 1.6 means the winning style got 1.6× the result), how many posts it rests on, a confidence from 1 to 5, and when it is due to be re-checked. Read these before writing a draft. The list is empty until a hook test has concluded — create_hook_test starts one. To score one particular caption against the rules, use check_draft instead.

  ConnectorAPI key

• get_account_statusA

  OneQAZ Trading IntelligenceA

  Purpose: Show which OneQAZ account (or API key) this connection uses, its plan and its rate limits. Requires a connected OneQAZ account — calling it without one prompts your AI app to connect (free, no API key needed; Pro users can use their key). All other tools work without an account. Triggers: "is my OneQAZ account connected?", "what plan am I on?", "내 OneQAZ 계정 상태", "남은 호출 한도". When to call: only when the user asks about their own account or limits. Output: full_data { principal (oauth|api_key), plan, usage {daily_limit, daily_used, minute_limit, ...}, account_id & connected_app (oauth only) }. Output nature: Service status and catalog information.

  ConnectorNo auth

• create_profileA

  ScriptGrainA

  Create a new voice profile from writing samples and start the stylometric extraction (45 measured attributes). Samples MUST be the user's own human-written prose — real emails, posts, articles or messages they wrote, never AI-generated text, or the profile captures the wrong voice. You can use writing you already hold for the user (messages they typed to you, documents or emails they shared, posts of theirs you can read): their exact words, never your memory notes or summaries about them, and never text you or another AI wrote or rewrote. Tell the user which pieces you are sending before you call this; the result's samples_used lists each piece's first line and word count so you can show them. 1-20 samples, each under 5,000 words; a sample needs 50+ words to count; 3+ samples totalling 3,000+ words gives a confident profile. Uses one of the plan's monthly extraction slots (rate limit: 5 extractions per hour); if refused for slots, get_billing shows the plan's extraction usage and remaining allowance. Extraction runs asynchronously, usually for under a minute (the longest take about two): poll get_profile until status is 'complete'.

  ConnectorAPI key