Summary
Add the content field to the LINEAR_CREATE_LINEAR_PROJECT and LINEAR_UPDATE_LINEAR_PROJECT actions in the Composio Linear toolkit, so that callers can set the full project body/description in a single call.
Background
Linear projects have a rich-text content field (the project body shown beneath the project header). Today, the Composio Linear toolkit's create_linear_project / update_linear_project actions do not expose this field, so the only way to populate the project body via Composio is to drop down to LINEAR_RUN_QUERY_OR_MUTATION and issue a raw GraphQL projectCreate / projectUpdate mutation.
That workaround is cumbersome for AI-agent workflows: the agent has to switch from a typed action to free-form GraphQL, manage variables/escaping itself, and lose the schema-level validation that the Composio action otherwise provides.
Reference (Linear GraphQL): ProjectCreateInput.content / ProjectUpdateInput.content, both String (markdown), already supported by Linear's API.
Proposed change
In Mercury's Linear app (/workspace/mercury/apps/linear/):
- Add an optional
content: strfield to the request schemas for the project create/update actions (markdown body). - Plumb the field through to the
projectCreate/projectUpdateGraphQL mutation ascontent. - Update the action descriptions / examples so the agent knows it can pass full markdown bodies.
- No breaking changes: the field is optional, default
None/ omit-if-missing.
Acceptance:
- Calling
LINEAR_CREATE_LINEAR_PROJECTwithcontent: "# Heading\n\nBody..."creates a Linear project whose body matches. - Calling
LINEAR_UPDATE_LINEAR_PROJECTwithcontent: ...updates the body without clobbering unrelated fields.