namely_create_announcement

Post an announcement to the company home feed, visible to every employee. Markdown; to mention a person write [Full Name](/people/<profile_id>). With is_appreciation, mentioned people are appreciated. email_all=true ALSO EMAILS every active employee at their company address (needs the permission) and cannot be undone: set it only when the user explicitly asks. Namely API: POST /events.

destructive

Argument	Type	Description
content*	string	Announcement text in markdown.
email_all	boolean	If true, also emails all active employees. Default false.
is_appreciation	boolean	If true, mentioned profiles are appreciated.

Input schema (JSON)

{
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "content"
  ],
  "properties": {
    "content": {
      "type": "string",
      "maxLength": 10000,
      "minLength": 1,
      "description": "Announcement text in markdown."
    },
    "email_all": {
      "type": "boolean",
      "description": "If true, also emails all active employees. Default false."
    },
    "is_appreciation": {
      "type": "boolean",
      "description": "If true, mentioned profiles are appreciated."
    }
  }
}

namely_create_event_comment

Add a comment to a feed event, posted as the token's user and visible to employees who see the event. Markdown; mention a person with [Full Name](/people/<profile_id>). Namely API: POST /events/{id}/comments.

destructive

Argument	Type	Description
content*	string	Comment text in markdown.
event_id*	string	Event id (from namely_list_events).

Input schema (JSON)

{
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "event_id",
    "content"
  ],
  "properties": {
    "content": {
      "type": "string",
      "maxLength": 10000,
      "minLength": 1,
      "description": "Comment text in markdown."
    },
    "event_id": {
      "type": "string",
      "minLength": 1,
      "description": "Event id (from namely_list_events)."
    }
  }
}

namely_get_group

Get one group by id, with the profiles (members) linked to it. Namely API: GET /groups/{id}.

read-only

Argument	Type	Description
id*	string	Group id (from namely_list_groups).

Input schema (JSON)

{
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "id"
  ],
  "properties": {
    "id": {
      "type": "string",
      "minLength": 1,
      "description": "Group id (from namely_list_groups)."
    }
  }
}

namely_get_me

Get the profile of the user the connected token belongs to (name, email, job title, manager, access role). Namely API: GET /profiles/me.

read-only

No arguments.

Input schema (JSON)

{
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "properties": {}
}

namely_get_profile

Get one employee's full profile by id: personal and job data, manager, groups, teams and the custom fields the token may see (can include compensation and other sensitive HR data). Namely API: GET /profiles/{id}.

read-only

Argument	Type	Description
id*	string	Namely profile id (the `id` of a profile from namely_list_profiles).

Input schema (JSON)

{
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "id"
  ],
  "properties": {
    "id": {
      "type": "string",
      "minLength": 1,
      "description": "Namely profile id (the `id` of a profile from namely_list_profiles)."
    }
  }
}

namely_get_report

Run a saved Namely report by id and return its columns and rows (live data; each row is a list in column order). Find the id in the URL of the report in Namely. Reports can contain sensitive HR data such as salary history. Namely API: GET /reports/{id}.

read-only

Argument	Type	Description
id*	string	Report id.

Input schema (JSON)

{
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "id"
  ],
  "properties": {
    "id": {
      "type": "string",
      "minLength": 1,
      "description": "Report id."
    }
  }
}

namely_get_team

Get one team by id, with the profiles (members) linked to it. Namely API: GET /teams/{id}.

read-only

Argument	Type	Description
id*	string	Team id (from namely_list_teams).

Input schema (JSON)

{
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "id"
  ],
  "properties": {
    "id": {
      "type": "string",
      "minLength": 1,
      "description": "Team id (from namely_list_teams)."
    }
  }
}

namely_list_event_comments

List the comments on a feed event. Namely API: GET /events/{event-id}/comments.

read-only

Argument	Type	Description
event_id*	string	Event id (from namely_list_events).

Input schema (JSON)

{
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "event_id"
  ],
  "properties": {
    "event_id": {
      "type": "string",
      "minLength": 1,
      "description": "Event id (from namely_list_events)."
    }
  }
}

namely_list_events

List events of the company home feed (announcements, birthdays, work anniversaries, new arrivals), newest first by default, with limit and after (an event id) for paging. Namely API: GET /events.

read-only

Argument	Type	Description
type	string	Event type, e.g. birthday, announcement, recent_arrival, anniversary.
after	string	Event id after which to start (for the next page).
limit	integer	Number of events to return (max 30).
order	string	Order by time; default desc.
profile_id	string	Only events associated with this profile id.

Input schema (JSON)

{
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "properties": {
    "type": {
      "type": "string",
      "description": "Event type, e.g. birthday, announcement, recent_arrival, anniversary."
    },
    "after": {
      "type": "string",
      "description": "Event id after which to start (for the next page)."
    },
    "limit": {
      "type": "integer",
      "maximum": 30,
      "minimum": 1,
      "description": "Number of events to return (max 30)."
    },
    "order": {
      "enum": [
        "asc",
        "desc"
      ],
      "type": "string",
      "description": "Order by time; default desc."
    },
    "profile_id": {
      "type": "string",
      "description": "Only events associated with this profile id."
    }
  }
}

namely_list_group_types

List the group types (the containers of groups, such as Department or Office). Namely API: GET /group_types.

read-only

No arguments.

Input schema (JSON)

{
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "properties": {}
}

namely_list_groups

List all groups (departments, office locations and other company groups). Every group belongs to one group type. Namely API: GET /groups.

read-only

No arguments.

Input schema (JSON)

{
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "properties": {}
}

namely_list_job_tiers

List all job tiers (the levels that group job titles). Namely API: GET /job_tiers.

read-only

No arguments.

Input schema (JSON)

{
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "properties": {}
}

namely_list_job_titles

List all job titles; each belongs to one job tier. Namely API: GET /job_titles.

read-only

No arguments.

Input schema (JSON)

{
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "properties": {}
}

namely_list_profile_fields

List the fields of the employee profile as configured at this company (standard and custom), with their labels, sections and the valid format of each value. Namely API: GET /profiles/fields.

read-only

No arguments.

Input schema (JSON)

{
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "properties": {}
}

namely_list_profiles

List employee profiles (active, pending and inactive unless filtered) with paging, sorting and filters. Returns {profiles, meta:{count}, linked}. Use format=short for a smaller record (ids, names, email, status, job title); the full record includes every custom field the token may see (compensation, addresses and other sensitive HR data). An empty page means the end. Namely API: GET /profiles (limit 100 requests per minute).

read-only

Argument	Type	Description
page	integer	Page number, starting at 1.
sort	string	Sort order; a leading - reverses it.
email	string	Exact company email.
format	string	short = truncated profile objects (default); full = every field.
per_page	integer	Profiles per page (default 30, max 50).
job_title	string	Exact job title (the `title` of a job title).
last_name	string	Exact last name.
first_name	string	Exact first name.

namely_list_teams

List all teams with their team categories. Namely API: GET /teams.

read-only

No arguments.

Input schema (JSON)

{
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "properties": {}
}

namely_update_profile

Change standard fields of an employee profile (name, emails, start date, status, manager, job title). WRITES live HR data. Send only the fields to change. Setting user_status to pending needs a personal_email. Namely API: PUT /profiles/{id}.

destructive

Argument	Type	Description
id*	string	Namely profile id (the `id` of a profile from namely_list_profiles).
email	string	Company email.
job_title	object	New job title: an object with the id or the exact title of an existing job title.
last_name	string	Last name.
first_name	string	First name.
reports_to	string	Profile id of the new manager.
start_date	string	Start date, YYYY-MM-DD.
user_status	string	active or pending.
personal_email	string	Personal email (required when user_status is pending).

Namely MCP by usefulapi

Try it

namely_create_announcement Destructive

Namely MCP by usefulapi

Try it

namely_create_announcement Destructive

Tools (17)