Skip to main content
Glama
contextstream

ContextStream MCP Server

Integration

integration
Read-onlyIdempotent

Execute integration actions across Slack, GitHub, and Notion: check status, search, get stats, track activity, and retrieve knowledge.

Instructions

Integration operations for Slack, GitHub, and Notion. Provider: slack, github, notion, all. Actions: status, search, stats, activity, contributors, knowledge, summary, channels (slack), discussions (slack), repos (github), issues (github), create_page (notion), create_database (notion), list_databases (notion), search_pages (notion with smart type detection - filter by event_type, status, priority, has_due_date, tags), get_page (notion), query_database (notion), update_page (notion), team_activity (aggregated team activity - team plans only).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
daysNoNumber of days for stats/summary (default: 7)
tagsNoFilter by tags, comma-separated (for Notion search_pages)
limitNoMaximum number of results to return.
queryNoSearch query string.
sinceNoISO 8601 timestamp to query changes since.
sortsNoSort order (for Notion query_database)
titleNoPage/database title (for Notion create_page/update_page/create_database)
untilNoInput parameter: until.
actionYesAction to perform
filterNoQuery filter (for Notion query_database)
statusNoFilter by status property, e.g. 'Done', 'In Progress' (for Notion search_pages)
contentNoPage content in Markdown (for Notion create_page/update_page)
page_idNoPage ID (for Notion get_page/update_page)
priorityNoFilter by priority property, e.g. 'High', 'Medium', 'Low' (for Notion search_pages)
providerYesIntegration provider
node_typeNoFilter knowledge by type (for Notion knowledge)
event_typeNoFilter by detected content type (for Notion search_pages)
project_idNoProject ID (UUID).
propertiesNoPage properties (for Notion update_page)
database_idNoDatabase ID (for Notion query_database/search_pages/activity)
descriptionNoDatabase description (for Notion create_database)
has_due_dateNoFilter to pages with or without due dates (for Notion search_pages)
workspace_idNoWorkspace ID (UUID).
parent_page_idNoParent page ID (for Notion create_page/create_database)
parent_database_idNoParent database ID (for Notion create_page). MUST call list_databases first - do NOT use IDs from memory
Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Contradiction between annotations (readOnlyHint=true) and description (includes create, update actions). Description doesn't reconcile this or add behavioral context beyond listing actions.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Description is a single paragraph that is front-loaded with purpose but becomes a dense list of actions and parameters. Some structure via parentheses and commas, but could be more concise.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (multiple providers, many actions), the description is incomplete. It omits details like the 'all' provider meaning, conditions for team_activity, and which actions apply to which providers. Schema fills gaps but description lacks completeness.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Input schema covers all 25 parameters with descriptions (100% coverage). The description adds context for some actions (e.g., search_pages filtering), but overall parameter semantics are adequately covered by schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool is for integration operations with Slack, GitHub, and Notion, listing providers and actions. It distinguishes from siblings which are not integration-focused. However, it bundles many actions into one tool, making it broad.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No explicit guidance on when to use this tool versus alternatives. The description merely lists actions without providing context-specific usage criteria or exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/contextstream/mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server