Searches the team's Marcora context library and returns up to 10 passages most relevant to a prompt, plus sources (each with a link_url) for citing. Read-only.

When to use:

• The user wants writing grounded in their team's brand or company context (blog post, email, social post, landing page, ad): call this with include_brand_foundation: true and write it yourself from what it returns. If asked to save it, use create_content content.

• The user asks about their own company, product, positioning, launches or competitors ("what do we have on competitor X?"): call it and answer from their context.

• Before saving text you wrote yourself through create_content / update_content content: those store it verbatim and consult no context.

When NOT to use:

• Before create_content with instructions (Marcora writes): it gathers the context itself.

• For brand voice, company overview, writing style or writing examples on their own: relevancy search never returns Brand Foundation. Use get_brand_foundation, or set include_brand_foundation: true here.

Inputs:

• prompt (required): what you need; be specific.

• include_brand_foundation: true on the FIRST call of a conversation (adds company overview, brand voice, style and examples); false or omitted after.

• include_only_me: true also searches the user's own Only me items (never another member's).

• project_id: adds that project's items and, on the first call, returns its project_brief. Read the brief before drafting: it outranks older chunks. Set include_project_brief: false on later calls for the same project.

• collection_ids and project_id broaden the search (additive, never an exclusive filter); dimension_option_ids biases toward an audience, persona or industry; context_rag_ids excludes chunks already returned when you page for more.

Present each link_url exactly as returned.

How results are ranked: each passage is scored on its own and against the whole document it belongs to, and the two scores are blended; weak matches are dropped, so fewer than 10 can come back. dimension_option_ids lean the ranking toward the chosen audience, persona or industry. It searches the reference library plus the project, collections and shared collections the user can access.

Only me items: by default only Team items are searched. With include_only_me: true the user's own Only me items, including Only me calls, are searched too, never another member's. Calls filed in Calls come back only when that Calls collection's id is in collection_ids, or through their project; on its own include_only_me: true returns none of them. If you then write material you read from an Only me source into a team-visible document, the write is refused until the user agrees.

Calls window: calls adds calls to the search: { date_from, date_to, kinds, companies }, every field optional (dates as YYYY-MM-DD or ISO 8601; kinds from customer, external, team_meeting, one_on_one, recorded; {} is every call you may use). Each call carries its date, kind and company in its heading. Only Team calls come back, never a teammate's Only me call; include_only_me: true adds your own Only me calls. A Team call filed in a private project or private collection is treated like an Only me call: its source carries audience: "only_me".

Sources: each sources entry carries the item name, content_type, audience (team or only_me), a link_url deep-link that opens the item in the Marcora web app (plus source_url, the original external page URL, for webpage items), its collection_id / project_id / last_updated, and the context_rag_ids from that item. Use these to cite or link the material you surface. (The previous top-level context_item_ids field has been replaced by sources; each source's context_item_id gives you the same IDs.)

Project brief: with project_id, the response carries a top-level project_brief block: the project's authoritative statement of premise, scope and the structural decisions already taken. It is the same block get_project returns (content_id, name, word_count, content_intro, truncated, read_first). Read it before drafting, revising, assessing or critiquing anything in the project; context chunks may be older than the brief or contradict it, and the brief wins. When truncated is true, content_intro is only the opening excerpt, so call get_content with its content_id for the full text. The brief is stored as content, not as a context item, so relevancy search never surfaces it: this block is the only way it reaches you from this tool. The key is absent when the project has no brief. include_project_brief defaults to true and is ignored without project_id.

Brand Foundation bundling: include_brand_foundation: true returns the team's Brand Foundation (company overview, brand voice, writing style, writing examples) in the same response. It is the always-on foundational context relevancy scoring never surfaces on its own. Pull it once, up front, so you have it for the rest of the session; you don't need it when handing off to create_content with instructions, which pulls it in automatically.

Errors when you pass project_id: "Project not found" means the project doesn't exist or belongs to a team other than your active team (check list_projects, or set_active_team if it is in another team). "You are not a member of project " means the project is private and you are not a member: ask a member to add you, or search without project_id. Neither error returns any context or brief.

Links: copy link_url character for character. Never retype, shorten, or rebuild a link or the IDs inside it.