跳至正文
OpenAgentSkill
浏览已开放 · 目录记录日期 2026-11-21 · 自动更新和账户服务暂时关闭。
效率与协作

famulor-assistants-history

Read Famulor assistant configurations, versions, catalogs, and omnichannel conversation history through the restricted Assistant & History MCP profile. Use for reviewing assistants or finding and summarizing call, messaging, or email history; never use it to change resources, send messages, place calls, run campaigns, manage telephony, or access billing.

bekservice · 已有 AI 审核记录

安装与使用

运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。

npx skills add bekservice/Famulor-Skill --skill famulor-assistants-history

技能说明


name: famulor-assistants-history description: Read Famulor assistant configurations, versions, catalogs, and omnichannel conversation history through the restricted Assistant & History MCP profile. Use for reviewing assistants or finding and summarizing call, messaging, or email history; never use it to change resources, send messages, place calls, run campaigns, manage telephony, or access billing. license: MIT metadata: author: bekservice version: "2.0.2" homepage: https://www.famulor.io

Famulor Assistants & Omnichannel History

Use the OAuth-secured Famulor MCP profile at:

https://app.famulor.io/mcp?profile=assistant-history

This marketplace profile is intentionally read-only. It exposes exactly 11 tools:

ToolUse
list_assistantsList assistants visible in the authenticated workspace.
get_assistantRead one assistant's configuration.
list_assistant_versionsList saved versions for an assistant.
get_assistant_versionRead one saved assistant version.
list_prompt_templatesList available prompt templates.
get_languagesList supported language options.
get_modelsList models available to the workspace.
get_voicesList available voices.
list_historySearch unified call, messaging, and email history.
get_callRead full details for one call returned by history.
get_email_history_itemRead the full email thread for one email history item.

Workflow

  1. Confirm which authenticated Famulor workspace the user means when it is ambiguous.
  2. Use a list_* tool to find the exact resource or history item instead of guessing an ID.
  3. Use the matching get_* tool when the user needs full detail.
  4. Summarize only the fields returned by the server and preserve the distinction between configured values and observed history.

list_history is the omnichannel overview. It may include voice calls, emails, and messaging conversations from connected channels such as Instagram or Messenger. Messaging entries can be previews rather than complete chat transcripts; never claim a full conversation unless the server actually returned it. Use get_call for call detail and get_email_history_item for an email thread.

Safety and access boundaries

  • Keep every request read-only. This profile cannot create, update, delete, send, call, launch, purchase, transfer, or configure anything.
  • Do not bypass the restricted profile when a user requests a write action. Explain that the installed marketplace integration supports Assistant & History review only.
  • Never infer access across workspaces. OAuth scopes, workspace membership, role, plan, retention, and server-side policy remain authoritative.
  • Treat transcripts, recordings, messages, emails, contacts, and customer context as personal data. Return only what is necessary for the request.
  • Use live tool schemas for arguments and availability; do not invent IDs, enum values, or fields.