Skip to main content
Glama
605,003 tools. Updated 2026-09-23 21:57

"Guide to Managing a CRM System" matching MCP tools:

  • Who am I? Returns the signed-in account: email, @handle, plan + limits, counts of sites/domains/drives, and connected DNS providers. Call this first to orient before managing sites or domains.
    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
  • Archive a CRM company (status inactive). Safer than delete — keeps counterparty and history. PATCH /api/crm/companies/:companyId. Scope write:crm; RBAC crm.leads.edit.
    Connector
    Destructive
    OAuth
  • Permanently delete a CRM company. Clears company links on leads/activities; does not delete the counterparty. Prefer crm_archive_company. DELETE /api/crm/companies/:companyId. Scope write:crm; RBAC crm.leads.edit.
    Connector
    Destructive
    OAuth
  • Get a Stripe billing portal URL for managing payment methods and invoices. Returns a URL (not a redirect) that the human can open in a browser. Requires: API key with read scope. Args: flow: Optional. Set to "payment_method_update" to go directly to the payment method update page. Returns: {"url": "https://billing.stripe.com/p/session/..."}
    ConnectorNo auth
  • Execute an OQL (OnePageCRM Query Language) query. Pass a JSON query object to read CRM data. Use describe() to discover entities and fields.
    ConnectorOAuth

Matching MCP Servers

Matching MCP Connectors

  • 中国 AI 客服国标 GB/T 47746—2026 合规问答库:必须自动转人工的场景、强制自查项、上线备案要求,答案标注条款依据。

  • Operate Obriym CRM from your AI assistant: leads, deals, orders, catalog, stock, marketplaces.

  • 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
  • Lists contacts in the tenant CRM — a person in the tenant CRM. Cursor-paginated: limit 1-100, opaque cursor from the previous page. Filters: q, company_id. Needs crm:read on the organization. Every item carries an absolute url. Being in the CRM is not permission to email: consent lives in the `marketing` sub-resource.
    ConnectorNo auth
  • List the caller's deliberation sessions, optionally filtered by status. Most useful for agents managing multiple concurrent sessions — use `status: 'ready'` to find sessions awaiting your next round. Returns a lightweight list (no response bodies); call `get_session` for full content.
    ConnectorNo auth
  • Return the user's personalization guide — how they want a person researched before you write to them. Call this only when you are going to personalize a message; follow the returned guide. When none is set, returns a note and you should fall back to the default research rules in the outreach craft skill.
    ConnectorOAuth
  • Edit a customer (client/contact) as the GUI CRM form does: name, email, phone, website, address, status, notes. Pass just the fields to change — omitted fields are untouched, an explicit empty string clears a text field, and a blank name is rejected. Errors if no field is given. Requires CRM-manager access. Verify with get_customer.
    ConnectorOAuth
  • Edit a sponsor as the GUI CRM form does: name, email, phone, website, status, tier, notes, metadata. Pass just the fields to change — omitted fields are untouched, an explicit empty string clears a text field, and a blank name is rejected. Errors if no field is given. Requires CRM-manager access. Verify with list_sponsors.
    ConnectorOAuth
  • Promote a model you own into a reusable template — flips it in place (no copy), so it keeps its content and stays editable, and surfaces in layerz_list_templates. The template's blueprint is derived on demand and its usage guide IS the model's FINANCE.md, so edit the guide later via layerz_set_finance_md on the same model. `scope` defaults to `user` (private, Pro feature). `scope: 'system'` publishes into the curated onboarding catalog visible to everyone and is admin-only. Not available for read-only or model-scoped API keys.
    ConnectorOAuth
  • Start a new property listing in YOUR agency's CRM from a description. Use when the agent is describing a property they have taken on and wants it in the system. Creates a DRAFT. It is never published and never appears on the portal from here: the agent adds photographs and the energy rating in the CRM and publishes it themselves. The response includes a direct link to the draft. Location is resolved against the real area tree, so a town, suburb or urbanisation name is enough. Requires an agency API key.
    ConnectorNo auth
  • Get the guide to authoring a wireframe mockup — the markup dialect, the wireframe component set, what the drawn style discards, and a complete valid example. Call this BEFORE composing your first mockup in a conversation: markup written from general Tailwind and HTML habits is refused, and the guide is what an author needs to write a mockup that is accepted first time.
    ConnectorOAuth
  • Update a CRM company. PATCH /api/crm/companies/:companyId — **companyId is `companies.id`**, not invoice customerId (counterparty id). `metadata` **replaces** the whole JSON object — GET the company first and merge. Set `metadata.billingTenantId` to the customer's control-plane tenant UUID for platform prepaid credit auto-grant on credits invoices (also syncs to counterparty). Scope write:crm; RBAC crm.leads.edit.
    ConnectorOAuth
  • Read a template in full: its blueprint plus its `description` — the markdown usage guide (what it is, how to use it, which business rules to fill). The guide IS the underlying model's FINANCE.md (a template's id equals its model id): to edit a template's guide, edit that model's FINANCE.md via layerz_set_finance_md — it propagates live, not as a snapshot. After forking or applying a template, follow the guide and update the new model's FINANCE.md so the conventions and objective match the project. Account-level, read-only.
    ConnectorOAuth
  • Read the full Lorg agent manual — includes all 5 contribution schemas, trust system rules, orientation guide, and API contract. Call this before contributing for the first time.
    ConnectorNo auth
  • Full use-case detail as a JSON+Markdown envelope: step guide, pros/cons, FAQ, tools used (JSON) + the full narrative guide (Markdown, full_md). null if unknown. Pass `fields` to project to only the keys you need (token-efficient).
    ConnectorNo auth
  • Retrieve one canonical Homechecker guide by slug. Use a slug returned by list_guides or search_guides. Returns source links, review metadata, method and limitations with the guide.
    ConnectorNo auth
  • Validate an API specification against style guide rules. Returns violations grouped by severity (error, warning, info) with rule details and affected paths. Use this to check against style guide rules; to check against the OpenAPI standard use validate_spec. Requires project context.
    ConnectorAPI key